Multi-merchant loyalty point partnership

ABSTRACT

A blockchain-based multi-merchant loyalty point partnership system may include a blockchain API host that receives a request to create a partnership smart contract for a multi-merchant loyalty point partnership. The request may specify various partnership parameters to include in the partnership smart contract. The blockchain API host may create the partnership smart contract and write the partnership smart contract to a blockchain. One or more qualified merchants may join the partnership smart contract to make the partnership active. In response to a customer completing a plurality of purchases that complete the partnership parameters of the partnership smart contract, the system may issue the customer a purchase reward which may include a loyalty point payout.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation-in-part of, and claims priority to,U.S. application Ser. No. 15/728,086 filed on Oct. 9, 2017 and entitled,“SYSTEMS AND METHODS FOR LOYALTY POINT DISTRIBUTION,” the contents ofwhich are hereby incorporated by reference in their entirety.

FIELD

This disclosure generally relates to loyalty points, and moreparticularly, to systems and methods for multi-merchant loyalty pointpartnerships using a distributed database.

BACKGROUND

Payment networks typically implement various systems for processingtransactions between merchants and customers. Merchants are members ofthe payment network and the merchants are authorized to charge tocustomer accounts. Customers have a transaction account with the paymentnetwork. To complete a transaction, a merchant typically transmits apayment request (or settlement) to the payment network with transactiondetails and the card member's account information. For payment networksusing loyalty points, options for using points are often limited to afew merchants.

Payment networks typically face increased costs and limitationsassociated with the traditional payment model. The payment networkimplements secure protocols for handling the payment requests, and suchsecure protocols along with network infrastructure are costly to developand maintain. The high network costs also result in high fees charged tomerchants using the payment network. Additional programs supported by apayment network such as loyalty points or multi-merchant loyalty pointpartnerships, for example, further increase costs associated withsecurity and infrastructure.

SUMMARY

Systems, methods, and articles of manufacture (collectively, the“system”) for multi-merchant loyalty point partnerships are disclosed.The system may receive a request create a partnership smart contract,wherein the request comprises a partnership parameter. The system maypropagate a contract request to consensus participants for writing to ablockchain, wherein the contract request comprises the partnership smartcontract, and wherein the partnership smart contract comprises thepartnership parameter. The system may transmit a contract writenotification to a loyalty portal, wherein in response to receiving thecontract write notification the loyalty portal broadcasts a partnershipnotification to a qualifying participant based on the partnershipparameter.

In various embodiments, the system may receive a request for an activepartnership smart contract, wherein the request comprises loyaltypartner data. The system may retrieve the active partnership smartcontract by comparing the partnership parameter of the activepartnership smart contract with the loyalty partner data. The system mayreturn the active partnership smart contract to a loyalty partner. Thesystem may receive a partnership enrollment request, wherein thepartnership enrollment request comprises loyalty partner data and apartnership smart contract identifier. The system may propagate thepartnership enrollment request to the consensus participants for writingto the blockchain, wherein in response to receiving the partnershipenrollment request the consensus participants achieve consensus on thepartnership enrollment request.

In various embodiments, the system may execute the partnership smartcontract in response to being invoked by a first loyalty partner,wherein the first loyalty partner invokes the blockchain API host inresponse to completing a first transaction with a customer, and whereinin response to being executed the partnership smart contract records thefirst transaction. The system may propagate a first transaction recordwrite to the consensus participants for writing to the blockchain,wherein in response to receiving the first transaction record write theconsensus participants achieve consensus on the first transaction recordwrite. The system may execute the partnership smart contract in responseto being invoked by a second loyalty partner, wherein the second loyaltypartner invokes the blockchain API host in response to completing asecond transaction with the customer, and wherein in response to beingexecuted the partnership smart contract records the second transaction.The system may propagate a second transaction record write to theconsensus participants for writing to the blockchain, wherein inresponse to receiving the second transaction record write the consensusparticipants achieve consensus on the second transaction record write.In response to being executed the partnership smart contract determinesthat the first transaction and the second transaction complete thepartnership parameter of the partnership smart contract.

In various embodiments, in response to a purchase reward of thepartnership smart contract being a loyalty point payout the partnershipsmart contract instructs blockchain API host to adjust a loyalty accountbalance of the customer based on the loyalty point payout. Thepartnership parameter may comprise at least one of a qualifyingparticipant parameter, a purchase requirement parameter, a purchasereward parameter, or a partnership duration parameter.

The forgoing features and elements may be combined in variouscombinations without exclusivity, unless expressly indicated hereinotherwise. These features and elements as well as the operation of thedisclosed embodiments will become more apparent in light of thefollowing description and accompanying drawings.

BRIEF DESCRIPTION

The subject matter of the present disclosure is particularly pointed outand distinctly claimed in the concluding portion of the specification. Amore complete understanding of the present disclosure, however, may beobtained by referring to the detailed description and claims whenconsidered in connection with the drawing figures, wherein like numeralsdenote like elements.

FIG. 1 illustrates a loyalty point or digital currency system configuredto operate on a public, private, or semi-private ledger maintained on ablockchain, in accordance with various embodiments;

FIG. 2 illustrates a process for registering users for a payment networkfor loyalty points using a blockchain-based ledger, in accordance withvarious embodiments;

FIG. 3 illustrates a process for shopping for loyalty point purchases ona website hosted by a merchant that accepts loyalty points as payment,in accordance with various embodiments;

FIG. 4 illustrates a process for checking a loyalty point balance on ablockchain-based ledger, in accordance with various embodiments;

FIG. 5 illustrates a process for a user to spend their loyalty points,in accordance with various embodiments;

FIG. 6 illustrates a process for peer-to-peer loyalty point transferusing a blockchain-based leger, in accordance with various embodiments;

FIG. 7 illustrates a process for adding a loyalty coalition member to ablockchain-based loyalty point system, in accordance with variousembodiments;

FIG. 8 illustrates a process for adding a currency exchange to ablockchain-based loyalty point system, in accordance with variousembodiments;

FIG. 9 illustrates a process for exchanging loyalty points for fiatcurrency, in accordance with various embodiments;

FIG. 10 illustrates a illustrates a loyalty point or digital currencysystem configured to for multi-merchant loyalty point partnerships, inaccordance with various embodiments;

FIG. 11 illustrates a process for generating a multi-merchant loyaltypoint partnership construct, in accordance with various embodiments;

FIG. 12 illustrates a process for enrolling a partner in amulti-merchant loyalty point partnership, in accordance with variousembodiments; and

FIG. 13 illustrates a process for customer-completion of themulti-merchant loyalty point partnership, in accordance with variousembodiments.

DETAILED DESCRIPTION

The detailed description of various embodiments herein makes referenceto the accompanying drawings and pictures, which show variousembodiments by way of illustration. While these various embodiments aredescribed in sufficient detail to enable those skilled in the art topractice the disclosure, it should be understood that other embodimentsmay be realized and that logical and mechanical changes may be madewithout departing from the spirit and scope of the disclosure. Thus, thedetailed description herein is presented for purposes of illustrationonly and not of limitation. For example, the steps recited in any of themethod or process descriptions may be executed in any order and are notlimited to the order presented. Moreover, any of the functions or stepsmay be outsourced to or performed by one or more third parties.Modifications, additions, or omissions may be made to the systems,apparatuses, and methods described herein without departing from thescope of the disclosure. For example, the components of the systems andapparatuses may be integrated or separated. Moreover, the operations ofthe systems and apparatuses disclosed herein may be performed by more,fewer, or other components and the methods described may include more,fewer, or other steps. Additionally, steps may be performed in anysuitable order. As used in this document, “each” refers to each memberof a set or each member of a subset of a set. Furthermore, any referenceto singular includes plural embodiments, and any reference to more thanone component may include a singular embodiment. Although specificadvantages have been enumerated herein, various embodiments may includesome, none, or all of the enumerated advantages.

A payment network based on peer-to-peer payments may be used tofacilitate most functions of traditional card payment networks and toenable additional services and functionality. For example, a blockchaindriven peer-to-peer payment network enables near-instant transactionauthorization and settlement. Payment, authorization, and/or settlementon such a network may result in money changing hands in an hour, 10minutes, a minute, or less depending on the infrastructure used toimplement the payment network. For a blockchain-based peer-to-peerpayment network, a governing organization or consortium may controlaccess to bank transfer services. Anyone can participate in the paymentnetwork, but in various embodiments, only users that registered with themanaging organization(s) may transfer earned credits into fiat currencyvia wire transfers to bank accounts. The blockchain may autonomouslymanage workflows associated with payment processing as described ingreater herein.

The payment networks use a distributed ledger maintained by a pluralityof computing devices (e.g., nodes) over a peer-to-peer network. Eachcomputing device maintains a copy and/or partial copy of the distributedledger and communicates with one or more other computing devices in thenetwork to validate and write data to the distributed ledger. Thedistributed ledger may use features and functionality of blockchaintechnology, including, for example, consensus based validation,immutability, and cryptographically chained blocks of data. Theblockchain may comprise a ledger of interconnected blocks containingdata. The blockchain may provide enhanced security because each blockmay hold individual transactions and the results of any blockchainexecutables. Each block may link to the previous block and may include atimestamp. Blocks may be linked because each block may include the hashof the prior block in the blockchain. The linked blocks form a chain,with only one successor block allowed to link to one other predecessorblock for a single chain. Forks may be possible where divergent chainsare established from a previously uniform blockchain, though typicallyonly one of the divergent chains will be maintained as the consensuschain.

The payment networks may also implement smart contracts that enforcedata workflows in a decentralized manner. For example, such paymentnetworks may enable digital currency smart contracts that enforcebusiness workflows in a decentralized manner and keep track of accountbalances. The payment networks may also enable reputation based smartcontracts that act as a directory of trustworthy entities as part of thepayment network.

A digital currency issuer may be included in the payment network and maybe configured to transfer balances between external banks and digitalcurrency based wallets vie electronic funds transfer (EFT) systems. Thedigital currency issuer may also connect customers with lenders toconvert lines of credit into digital currencies. The payment network mayalso include digital wallet services deployed on user devices such as,for example, computers, tablets, smartphones, Internet of Things devices(IoT devices), etc. The digital wallet services may enable payments byinteracting with the smart contracts and the blockchain underpinning thepayment network.

FIG. 1 depicts a loyalty point network 100 that operates on a blockchain102, in accordance with various embodiments. Loyalty point network 100may also contemplate uses in association with web services, utilitycomputing, pervasive and individualized computing, security and identitysolutions, autonomic computing, cloud computing, commodity computing,mobility and wireless solutions, open source, biometrics, gridcomputing, and/or mesh computing.

Blockchain 102 may be a distributed database that maintains records in areadable manner and that is resistant to tampering. Blockchain 102 maybe based on blockchain technologies such as, for example, ETHEREUM®,Open Chain, Chain Open Standard, HYPERLEDGER® Fabric, CORDA CONNECT®,INTEL® Sawtooth, etc. Blockchain 102 may comprise a ledger ofinterconnected blocks containing data. Each block may link to theprevious block and may include a timestamp. The blocks can hold filetransfer data, smart contract data, and/or other information as desired.Each block may link to the previous block and may include a timestamp.Blockchain 102 may be maintained on various blockchain nodes (e.g.,consensus participants 103), and may be maintained in the form of copiesor partial copies of the blockchain 102, as discussed further herein.Blocks may be written to blockchain 102 by establishing consensusbetween the blockchain nodes. For example, consensus may be establishedbased on proof of work, proof of stake, practical byzantine faulttolerance, delegated proof of stake, or other suitable consensusalgorithms. When implemented in support of loyalty point network 100,the blockchain may serve as an immutable log for loyalty pointtransactions and registrations.

blockchain 102 may be maintained in a peer-to-peer network that isprivate, consortium and/or public in nature (ETHEREUM®, HYPERLEDGER®Fabric, etc.). Consortium and private networks may offer improvedcontrol over the content of the blockchain and public networks mayleverage the cumulative computing power of the network to improvesecurity. In that regard, blockchain 102 may be implemented usingtechnologies such as, for example, ETHEREUM® GETH, eth-lightwallet, orother suitable or future blockchain interface technologies.

In various embodiments, blockchain 102 may be maintained by consensusparticipants 103 in the form of computing devices configured to validateblocks of the blockchain. Loyalty point network 100 comprises aplurality of blockchain API hosts 104 that communicate with blockchain102 in response to receiving API calls from various other computingdevices and systems seeking to read from or write to blockchain 102.Blockchain API hosts 104 and other computing devices described hereinmay take the form of a computer or processor, or a set of computers,processor, and/or application specific integrated circuits (ASICs),although other types of computing units or systems may be used.Exemplary computing devices may include servers, pooled servers,laptops, notebooks, hand held computers, personal digital assistants,cellular phones, smart phones (e.g., IPHONE®, BLACKBERRY®, ANDROID®,etc.), tablets, wearables (e.g., smart watches, smart glasses, etc.),interne of things (IoT) devices, or any other device capable ofreceiving data over a network. Each computing device may runapplications to interact with blockchain 102, communicate with otherdevices, perform crypto operations, and otherwise operate within loyaltypoint network 100. For example, each computing device may run a clientapplication that can be a thin client (web), a hybrid (e.g., web andnative, such as APPLE® iOS and ANDROID®), or a native application tomake application programming interface (API) calls to blockchain APIhost 104 and interact with blockchain 102, such as a web3 API compatiblewith blockchain databases maintained by ETHEREUM®.

In various embodiments, blockchain API hosts 104 may host an outwardfacing API 108 accessible by communication over a network such as, forexample, a LAN, a WAN, the internet, and/or any other suitable type ofnetwork discussed herein.

In various embodiments, API 108 may serve as a blockchain interfaceaccessible by applications and computing devices of loyalty pointnetwork 100. API 108 may be implemented using technologies such as, forexample, ETHEREUM® GETH, eth-lightwallet, or other suitable blockchaininterface technologies. Loyalty wallets 105 may communicate withblockchain API host 104 using API 108. Loyalty wallet 105 may checkloyalty point balances, adjust loyalty point balances, transfer loyaltypoints, register a user or device, or otherwise manipulate loyaltypoints as allowed by loyalty point network 100. Loyalty wallet 105A, forexample, may run on a mobile device to enable customer 109 to interactwith blockchain 102 and his or her loyalty points.

In various embodiments, merchants that accept loyalty points fromloyalty point network 100 as a form of payment may host loyalty partnersites 106 on computing devices. Customer 109 may browse or searchloyalty partner site 106 for items in a manner similar to typicalecommerce sites. Once customer 109 has selected items for purchase,customer 109 may purchase the items using loyalty points. Loyaltypartner sites 106 may thus communicate with blockchain 102 throughblockchain API host 104 using API 108 to complete purchase transactionsusing loyalty points.

In various embodiments, currency exchange sites 107 may exchange loyaltypoints from customer 109 into fiat currency. Currency exchange sites mayinclude web sites hosted on computing devices remote from customer 109and/or brick and mortar locations such as currency exchange stores.Currency exchange sites 107 may communicate with blockchain 102 throughblockchain API host 104 using API 108.

In various embodiments, loyalty point network 100 may include controlsto restrict access to registered loyalty partner sites 106 and/orcurrency exchange sites 107. Certificate authority 112 may allowparticipants to join loyalty point network 100 or may disallow would-beparticipants from joining loyalty point network 100. Certificateauthority may communicate with blockchain 102 through consensusparticipants 103 of blockchain 102 using an API 108. Certificateauthority 112 may include a web interface for review of new currencyexchange sites by currency exchange candidate staff 113. Similarly,certificate authority 112 may include a web interface for review of newloyalty partner sites by loyalty coalition candidate staff 111. Thestaff members may thus approve or deny candidates for joining loyaltypoint network 100. Validation may include verifying of proof of identitysuch as, for example, phone number, employer ID, SSN, or any sensitiveinformation that known by the employees of the respective entity.

As used herein, “transmit” may include sending at least a portion ofelectronic data from one system component to another. Additionally, asused herein, “data,” “information,” or the like may include encompassinginformation such as commands, queries, files, messages, data forstorage, and the like in digital or any other form.

As used herein, “electronic communication” may comprise a physicalcoupling and/or non-physical coupling capable of enabling systemcomponents to transmit and receive data. For example, “electroniccommunication” may refer to a wired or wireless protocol such as a CANbus protocol, an Ethernet physical layer protocol (e.g., those using10BASE-T, 100BASE-T, 1000BASE-T, etc.), an IEEE 1394 interface (e.g.,FireWire), Integrated Services for Digital Network (ISDN), a digitalsubscriber line (DSL), an 802.11a/b/g/n/ac signal (e.g., Wi-Fi), awireless communications protocol using short wavelength UHF radio wavesand defined at least in part by IEEE 802.15.1 (e.g., the BLUETOOTH®protocol maintained by Bluetooth Special Interest Group), a wirelesscommunications protocol defined at least in part by IEEE 802.15.4 (e.g.,the ZIGBEE® protocol maintained by the ZigBee alliance), a cellularprotocol, an infrared protocol, an optical protocol, or any otherprotocol capable of transmitting information via a wired or wirelessconnection.

One or more of the system components may be in electronic communicationvia a network. As used herein, the term “network” may further includeany cloud, cloud computing system, or electronic communications systemor method that incorporates hardware and/or software components.Communication amongst the nodes may be accomplished through any suitablecommunication channels, such as, for example, a telephone network, anextranet, an intranet, Internet, point of interaction device (personaldigital assistant, cellular phone, kiosk, tablet, etc.), onlinecommunications, satellite communications, off-line communications,wireless communications, transponder communications, local area network(LAN), wide area network (WAN), virtual private network (VPN), networkedor linked devices, keyboard, mouse and/or any suitable communication ordata input modality. Moreover, although the system is frequentlydescribed herein as being implemented with TCP/IP communicationsprotocols, the system may also be implemented using Internetwork PacketExchange (IPX), APPLETALK® program, IP-6, NetBIOS, OSI, any tunnelingprotocol (e.g. IPsec, SSH, etc.), or any number of existing or futureprotocols. If the network is in the nature of a public network, such asthe internet, it may be advantageous to presume the network to beinsecure and open to eavesdroppers. Specific information related to theprotocols, standards, and application software utilized in connectionwith the Internet is generally known to those skilled in the art and, assuch, need not be detailed herein.

“Cloud” or “Cloud computing” includes a model for enabling convenient,on-demand network access to a shared pool of configurable computingresources (e.g., networks, servers, storage, applications, and services)that can be rapidly provisioned and released with minimal managementeffort or service provider interaction. Cloud computing may includelocation-independent computing, whereby shared servers provideresources, software, and data to computers and other devices on demand.For more information regarding cloud computing, see the NIST's (NationalInstitute of Standards and Technology) definition of cloud computing.

The various system components may be independently, separately orcollectively suitably coupled to the network via data links whichincludes, for example, a connection to an Internet Service Provider(ISP) over the local loop as is typically used in connection withstandard modem communication, cable modem, DISH NETWORKS®, ISDN, DSL, orvarious wireless communication methods. It is noted that the network maybe implemented as other types of networks, such as an interactivetelevision (ITV) network. Moreover, the system contemplates the use,sale or distribution of any goods, services or information over anynetwork having similar functionality described herein.

A network may be unsecure. Thus, communication over the network mayutilize data encryption. Encryption may be performed by way of any ofthe techniques now available in the art or which may becomeavailable—e.g., Twofish, RSA, El Gamal, Schorr signature, DSA, PGP, PM,GPG (GnuPG), HPE Format-Preserving Encryption (FPE), Voltage, TripleDES, Blowfish, AES, MD5, HMAC, IDEA, RC6, and symmetric and asymmetriccryptosystems. Network communications may also incorporate SHA seriescryptographic methods, elliptic-curve cryptography (e.g., ECC, ECDH,ECDSA, etc.), and/or other post-quantum cryptography algorithms underdevelopment.

For the sake of brevity, conventional data networking, applicationdevelopment, and other functional aspects of system may not be describedin detail herein. Furthermore, the connecting lines shown in the variousfigures contained herein are intended to represent exemplary functionalrelationships and/or electronic communications between the variouselements. It should be noted that many alternative or additionalfunctional relationships or electronic communications may be present ina practical system.

Referring now to FIGS. 2-9 the process flows and screenshots depictedare merely embodiments and are not intended to limit the scope of thedisclosure. For example, the steps recited in any of the method orprocess descriptions may be executed in any order and are not limited tothe order presented. It will be appreciated that the followingdescription makes appropriate references not only to the steps and userinterface elements depicted in FIGS. 2-9, but also to the various systemcomponents as described above with reference to FIG. 1. It should beunderstood at the outset that, although exemplary embodiments areillustrated in the figures and described below, the principles of thepresent disclosure may be implemented using any number of techniques,whether currently known or not. The present disclosure should in no waybe limited to the exemplary implementations and techniques illustratedin the drawings and described below. Unless otherwise specificallynoted, articles depicted in the drawings are not necessarily drawn toscale.

Referring to FIG. 2, an exemplary registration process 200 is shown forloyalty point network 100, in accordance with various embodiments.Customer 109 may download and install a loyalty wallet 105 on his or hermobile device (Step 201). Loyalty wallet 105 may be in electroniccommunication with blockchain API host 104 over a network. Loyaltywallet 105 may generate and/or receive an asymmetric cryptography keypair including a private key paired with a public key (Step 202).Loyalty wallet 105 may display a mnemonic seed and password selectionscreen to customer 109, and it may use BIP32, BIP39, BIP44, or anotherkey generation technique to create public keys (e.g., blockchainaddresses) and private keys, which may be encrypted and stored locallyon the customer's computing device.

In various embodiments, loyalty wallet 105 may encrypt the private keyand securely store the private key for later use. Loyalty wallet 105 mayalso collect personal information from customer 109 (Step 203). Aregistration form may, for example, include fields for customer 109 toenter a user name and enter a password. Customer 109 may enter usercredentials comprising a user ID, password, and any other informationentered into the registration form of loyalty wallet 105.

In various embodiments, loyalty wallet 105 may prepare and sign aregistration request for transmission to a blockchain API host 104 (Step204). The registration request may include the personal information ofcustomer 109 (collected in step 203), the public key (generated in step202), an application ID, a device ID, an account number, or otherinformation germane to registration. In that regard, the blockchainaddress may be associated with the customer's loyalty point account. Thesignature may be a crypto operation performed with the private key fromthe asymmetric key pair (generated in step 202). Loyalty wallet 105 maytransmit the registration request to blockchain API host 104 (Step 205).Loyalty wallet 105 may make an API call to transmit the registrationrequest.

In various embodiments, blockchain API host 104 may verify the signatureand prepare a proposal to register customer 109 (Step 206). BlockchainAPI host 104 may verify the signature by performing a crypto operationusing the public key to the data that was signed using the private key.Blockchain API host 104 may propagate the registration proposal toconsensus participants 103 (Step 207). Blockchain API host 104 maypropagate the registration proposal by writing it to the blockchain orby otherwise transmitting the proposal to consensus participants 103.Consensus participants 103 may achieve consensus and add a new ledgerfor customer 109 to blockchain 102 (Step 208). Consensus participants103 may validate registrations, loyalty point transactions, and anyother activity on blockchain 102 by establishing consensus between theparticipants based on proof of work, proof of stake, practical byzantinefault tolerance, delegated proof of stake, or other suitable consensusalgorithms. Consensus participants 103 may notify loyalty wallet 105 ofsuccessful registration by transmitting a confirmation, or by loyaltywallet locating the registration written on blockchain 102 (Step 209).

With reference to FIG. 3, process 300 is shown for shopping for onloyalty point network 100, in accordance with various embodiments.Customer 109 shops with a loyalty partner by browsing loyalty partnersite 106 (Step 301). Loyalty partner site 106 may prompt customer 109and/or loyalty wallet 105 for the corresponding loyalty account atcheckout (Step 302). The loyalty account may be identifiable by auniversally unique identifier (UUID), for example. Customer 109 mayprovide the loyalty account (Step 303) in response to the prompt byentering the loyalty account and/or by loyalty wallet 105 transmittingthe loyalty account.

In various embodiments, loyalty partner site 106 may transmit a pointadjustment request to blockchain API host 104 (Step 304) using an APIcall. Blockchain API host 104 may execute a smart contract (Step 305) inresponse to receiving the API request to adjust a point balance.Blockchain API host 104 may also send adjustment request to the networkof consensus participants 103 (Step 306). Consensus participants 103 mayachieve consensus and thus new entry to blockchain 102 (Step 307).Consensus participants 103 may notify loyalty partner site 106 (Step308) of the completed balance adjustment. Consensus participants 103 mayalso notify customer 109 (Step 309) of the completed balance adjustment.

With reference to FIG. 4, a process 400 is shown for checking a loyaltypoint balance in loyalty point network 100, in accordance with variousembodiments. Customer 109 request his or her loyalty point balance inloyalty wallet 105 (Step 401). Loyalty wallet 105 may prepare and/orsign the request (Step 402). Loyalty wallet 105 may sign the request byperforming a crypto operation with a private key from an asymmetriccryptographic key pair as described above. Loyalty wallet 105 maytransmit the signed request to blockchain API host 104 (Step 403).

In various embodiments, blockchain API host 104 may validate thesignature and prepare a proposal to inquire point balance (Step 404).Blockchain API host 104 may validate the signature by performing acryptographic operation using the public key on the data what wasencrypted by loyalty wallet 105 using the corresponding private key.Blockchain API host 104 may prepare the proposal by preparing data forwriting to a block of the blockchain including, for example, anidentifier of the customer (e.g., the public key or blockchain address),the transaction (e.g., a balance inquiry), the requesting party, atimestamp, or any other data for inclusion in the blockchain.

In various embodiments, blockchain API host 104 may propagate theproposal to consensus participants 103 by transmitting the proposaland/or writing the proposal to blockchain 102 (Step 405). Consensusparticipants 103 may achieve consensus and add the proposal to theblockchain 102 (Step 406). The consensus participants 103 and/orblockchain API host 104 may notify customer 109 by writing to blockchain102 and/or transmitting a confirmation and/or a balance to loyaltywallet 105 (Step 407).

Referring now to FIG. 5, a process 500 is shown for spending loyaltypoints with a loyalty partner site 106 of loyalty point network 100, inaccordance with various embodiments. Customer 109 may shop on a loyaltypartner site 106 using a website or native application (Step 501).Loyalty partner site 106 may host a checkout page (Step 502). Thecheckout page may offer various payment methods such as credit, ACH,gift cards, and loyalty points, for example. Customer 109 may selectloyalty points as a payment method on loyalty partner site 106 (Step503).

In response to the selection of loyalty points as a payment method, acomputing device may open loyalty wallet 105 installed on the computingdevice by a deep link (Step 504). A deep link allows a first applicationrunning on a computing device to launch a second application installedon the computing device and/or pass data from the first application tothe second application. For example, web browsers running on mobiledevices often launch an application store to facilitate installation ofa particular application on the mobile device. Here, the deep linktriggered by selecting points as a payment method may launch loyaltywallet 105 and send as parameters the merchant blockchain account (e.g.,the merchant's public key) and the amount of purchase.

In various embodiments, the computing device may prompt for a securitypassword to access loyalty wallet 105 (Step 505), and the computingdevice may receive and/or authenticate the password from customer 109(Step 506). The password may be in the form of a pin, passcode,password, biometric identifier, one-time password, or other datasuitable for authenticating customer 109. Loyalty wallet 105 may decryptthe private key stored on the computing device and sign a request to payloyalty partner site 106 using loyalty points (Step 507). The requestmay include the data passed to loyalty wallet 105 by the deep link inresponse to loyalty partner site 106 launching loyalty wallet 105. Forexample, the request may include the merchant's blockchain address andthe amount of purchase.

In various embodiments, loyalty wallet 105 may send the payment requestto blockchain API host 104 (Step 508). Blockchain API host 104 mayvalidate the signature in response to receiving the request byperforming a cryptographic operation using the public key on the datathat was encrypted by loyalty wallet 105 using the corresponding privatekey. Blockchain API host 104 may prepare the proposal by preparing datafor writing to a block of the blockchain including, for example, thecustomer's blockchain address (e.g., the public key), the transaction(e.g., a payment), a transaction amount, the merchant's blockchainaddress, a timestamp, or any other data for inclusion in the blockchain.

In various embodiments, blockchain API host 104 may propagate theproposal to consensus participants 103 by transmitting the proposaland/or writing the proposal to blockchain 102 (Step 510). Consensusparticipants 103 may achieve consensus and add the proposal to theblockchain 102 (Step 511). The consensus participants 103 and/orblockchain API host 104 may thus notify customer 109 by writing datafrom the proposal to blockchain 102 and/or transmitting a confirmationto loyalty wallet 105 (Step 512). Once written to the blockchain, thedata from the proposal updates the account balance for customer 109 byremoving the amount of loyalty points spent with loyalty partner site106.

With reference to FIG. 6, a process 600 is shown for peer-to-peertransfer of loyalty points in loyalty point network 100, in accordancewith various embodiments. Customer 109 may request a peers' account(Step 601). The account may be sent to the customer via a message oremail, for example, and may come in the form of the peer's public key,UUID, and/or blockchain address. Loyalty wallet 105 may fetch the peer'saddress (Step 602). For example, loyalty wallet 105 may scan acommunication channel to identify the account, may allow customer 109 toenter the account, or may communicate with a loyalty wallet belonging tothe peer to receive the account.

In various embodiments, loyalty wallet 105 running on the customer'scomputing device may prompt customer 109 for a security password (Step603), and the computing device may receive and/or authenticate thepassword from customer 109 (Step 604). The password may be in the formof a pin, passcode, password, biometric identifier, one-time password,or other data suitable for authenticating customer 109. Loyalty wallet105 may decrypt the private key stored on the computing device and signa request to transfer loyalty points to the peer's account (Step 605).The request may include, for example, the peer's account and the amountof points for transfer to the peer.

In various embodiments, loyalty wallet 105 may send the transfer requestto blockchain API host 104 (Step 606). Blockchain API host 104 mayvalidate the signature and prepare a proposal in response to receivingthe request (Step 607). Blockchain API host 104 may validate thesignature by performing a cryptographic operation using the public keyon the data that was encrypted by loyalty wallet 105 using thecorresponding private key. Blockchain API host 104 may also prepare atransfer proposal by preparing data for writing to a block of theblockchain with the data including, for example, the customer'sblockchain address (e.g., the public key), the transaction (e.g., atransfer), the peer's account (e.g., blockchain address), a timestamp,the transfer amount, or any other data for inclusion in the blockchain.

In various embodiments, blockchain API host 104 may propagate theproposal to consensus participants 103 by transmitting the proposaland/or writing the proposal to blockchain 102 (Step 608). Consensusparticipants 103 may achieve consensus and add the proposal to theblockchain 102 (Step 609). The consensus participants 103 and/orblockchain API host 104 may thus notify customer 109 by writing datafrom the proposal to blockchain 102 and/or transmitting a confirmationto loyalty wallet 105 (Step 610). Once written to the blockchain, thedata from the proposal updates the account balances for customer 109 andthe peer by transferring the requested amount of loyalty points from thecustomer's account to the peer's account.

With reference to FIG. 7, process 700 is shown for adding a loyaltycoalition member such as a new loyalty partner, in accordance withvarious embodiments. The candidate staff 111 may register an entity withcertificate authority 112 (Step 701). Certificate authority 112 mayrespond by providing certificates and/or private keys to the loyaltycoalition candidate staff 111 (Step 702). Loyalty coalition candidatestaff may prepare a request to add the entity as a new coalition member,sign the request, and transmit the request to blockchain API host 104(Step 703). The request may be signed by performing a cryptographicoperation on all or part of the request using the private key receivedfrom the certificate authority 112.

In various embodiments, blockchain API host 104 may verify the signatureby performing a cryptographic operation on the signed data using thepublic key corresponding to the entity's private key (Step 704).Blockchain API host 104 may also prepare a proposal to add the entity toloyalty point network 100. Blockchain API host 104 may propagate theproposal to consensus participants 103 by transmitting the proposaland/or writing the proposal to blockchain 102 (Step 705). Consensusparticipants 103 may achieve consensus and add the proposal to theblockchain 102 (Step 706). The consensus participants 103 and/orblockchain API host 104 may thus notify loyalty coalition candidatestaff 111 by writing data from the proposal to blockchain 102 and/ortransmitting a confirmation to loyalty wallet 105 (Step 707). Oncewritten to the blockchain, the data from the proposal adds the entity tothe loyalty payment network of network 100.

With reference to FIG. 8, a process 800 for adding a currency exchangeto loyalty point network 100 is shown, in accordance with variousembodiments. The candidate staff 113 working on behalf of theregistering entity may register an entity with certificate authority 112(Step 801). Certificate authority 112 may respond by providingcertificates and/or private keys to the currency exchange candidatestaff 113 (Step 802). Currency exchange candidate staff 113 may preparea request to add the entity as a currency exchange, sign the request,and transmit the request to blockchain API host 104 (Step 803). Therequest may be signed by performing a cryptographic operation on all orpart of the request using the private key received from the certificateauthority 112.

In various embodiments, blockchain API host 104 may verify the signatureby performing a cryptographic operation on the signed data using thepublic key corresponding to the entity's private key (Step 804).Blockchain API host 104 may also prepare a proposal to add the entity toloyalty point network 100 as a currency exchange. Blockchain API host104 may propagate the proposal to consensus participants 103 bytransmitting the proposal and/or writing the proposal to blockchain 102(Step 805). Consensus participants 103 may achieve consensus and add theproposal to the blockchain 102 (Step 806). The consensus participants103 and/or blockchain API host 104 may thus notify currency exchangecandidate staff 113 by writing data from the proposal to blockchain 102and/or transmitting a confirmation to loyalty wallet 105 (Step 807).Once written to the blockchain, the data from the proposal adds theentity to the loyalty payment network of network 100 as a currencyexchange.

Referring now to FIG. 9, a process 900 is shown for exchanging loyaltypoints for fiat currency in loyalty point network 100, in accordancewith various embodiments. Customer 109 accesses on a currency exchangesite 107 using a website or native application to request a currencyexchange rate (Step 901). Currency exchange site 107 may provideexchange rates from loyalty points into one or more fiat currenciesand/or from fiat currencies into loyalty points (Step 902). Customer 109may provide to currency exchange site 107 exchange information inrequesting the currency exchange (Step 903). The exchange informationmay include destination account for the fiat currency, ACH details,currency type, currency amount, or other data.

In response to the request for a currency exchange, a computing devicemay open loyalty wallet 105 installed on the computing device by a deeplink (Step 904). The deep link triggered by requesting a currencyexchange from points to fiat currency may launch loyalty wallet 105 andsend as parameters the requested fiat currency type, the requested fiatcurrency amount, the amount of loyalty points to exchange, and/or theaccount of the currency exchange (e.g., the exchange's public key,UUID).

In various embodiments, the computing device may prompt for a securitypassword to access loyalty wallet 105 (Step 905), and the computingdevice may receive and/or authenticate the password from customer 109(Step 906). The password may be in the form of a pin, passcode,password, biometric identifier, one-time password, or other datasuitable for authenticating customer 109. Loyalty wallet 105 may decryptthe private key stored on the computing device and sign a request toexchange currency with currency exchange site 107 (Step 907). Therequest may include the data passed to loyalty wallet 105 by the deeplink in response to currency exchange site 107 launching loyalty wallet105. For example, the request may include the exchange's account, theamount of loyalty points to exchange, and the fiat currency type.

In various embodiments, loyalty wallet 105 may send the exchange requestto blockchain API host 104 (Step 908). Blockchain API host 104 mayvalidate the signature in response to receiving the request byperforming a cryptographic operation using the public key on the datathat was encrypted by loyalty wallet 105 using the corresponding privatekey (Step 909). Blockchain API host 104 may prepare the proposal bypreparing data for writing to a block of the blockchain including, forexample, the customer's blockchain address (e.g., the public key), thetransaction (e.g., a currency exchange), an exchange amount, themerchant's blockchain address, a timestamp, or any other data forinclusion in the blockchain.

In various embodiments, blockchain API host 104 may propagate theproposal to consensus participants 103 by transmitting the proposaland/or writing the proposal to blockchain 102 (Step 910). Consensusparticipants 103 may achieve consensus and add the proposal to theblockchain 102 (Step 911). The consensus participants 103 and/orblockchain API host 104 may thus notify the currency exchange by writingdata from the proposal to blockchain 102 and/or transmitting aconfirmation to currency exchange site 107 (Step 912). Once written tothe blockchain, the data from the proposal updates the account balancefor customer 109 by removing the amount of loyalty points exchanged withcurrency exchange site 107. The currency exchange may credit the bankaccount identified to currency exchange site 107 with the fiat currencyamount (Step 913). The currency exchange may use an ACH transfer tocredit customer 109 with the account and transfer information entered bycustomer 109 (in Step 903). Currency exchange site 107 may notifyloyalty wallet 105 in response to completion of the exchange (Step 914).The notification may take the form of a text message, email, or pushnotification, for example.

In various embodiments, and with reference to FIG. 10, loyalty pointnetwork 100 may also be configured to facilitate multi-merchant loyaltypoint partnerships. Merchants (e.g., loyalty partners) may desire tocreate partnerships with one or more other merchants to incentivizecustomers 109 to purchase goods or services at each merchant joined inthe partnership. For example, merchants in a common industry (e.g.,hotel, airline, etc.) may form a partnership to incentivize customers topurchase from one or more merchants in the industry. Loyalty pointnetwork 100 may incentivize partner merchants and/or customers 109 byproviding a partnership reward, such as a loyalty point payout, inresponse to customer 109 purchasing goods or services at each merchant,in accordance with the partnership.

The loyalty point network 100 may enable SKU-level based rewardsbonusing with merchant partners, partner discounts and/or the loyaltypartner credits by rewarding partners, merchants and/or customers 109.In response to customer 109 conducting a purchase transaction for goodsor services at a merchant, the merchant may acquire a bar code, UPCand/or SKU from the product or packaging. The UPC and/or SKU may be inthe form of a bar code, data, QR code or other code or symbol. The UPCand/or SKU may be scanned by the merchant POS to acquire the data fromthe product. The UPC and/or SKU may include data about the product, themerchant, the manufacturer, contents, health data, etc. Such data (orany subset of such data) may be used to determine a loyalty point amountor payout to customer 109 and/or to a merchant. For example, the SKUdata may disclose that the customer purchased 3 Wilson tennis rackets.The manufacturer Wilson or the merchant selling the product (or anyother entity in the supply chain) may agree to provide or fund a certainamount of reward points (for the partner, merchant and/or customer)based on buying 2 or more Wilson tennis rackets during a certaintimeframe or for a certain price, etc. For more information about SKUbased rewards, see U.S. Pat. Nos. 8,065,182, 8,024,220, 7,813,955,7,672,870, 7,613,628, 7,496,524, 7,428,498, 7,398,226 and 7,398,225,which all are hereby incorporated by reference in their entirety for allpurposes.

For example, travel merchants may desire to create partnerships centeredaround a travel package (e.g., purchase a flight from merchant A, ahotel from merchant B, a dinner at merchant C, a rental car frommerchant D, etc.). As discussed further herein, a merchant may invoke asmart contract and may specify one or more merchants, or desiredcharacteristics of partner merchants, to form a partnership. The smartcontract may set forth the purchase requirements at each merchant, apartnership duration (e.g., a day, a week, a month, etc.), parametersfor the loyalty point payout or reward, and any other desired parameter.In response to a customer 109 completing at least a portion of thepurchase requirements at each merchant (or a subset of the merchants),customer 109 may receive at least a portion of the loyalty point payoutor other reward. Customer 109 may redeem the loyalty points at variousloyalty partner sites 106, or may exchange the loyalty points into afiat or cryptocurrency, as previously discussed.

In various embodiments, loyalty point network 100 may comprise a loyaltyportal 1040. Loyalty portal 1040 may be configured to enable merchantsto create and/or join various multi-merchant loyalty point partnerships,as discussed further herein. Loyalty portal 1040 may comprise software,a mobile application, a web interface, or the like. Loyalty portal 1040may be accessible to loyalty partners directly via a graphical userinterface (“GUI”) in a web browser, native application, or the like.Loyalty portal 1040 may include one or more software modules, logicengines, various databases, interfaces to systems and tools, and/orcomputer networks. In various embodiments, loyalty portal 1040 may beintegrated into, or be in electronic communication with, one or moresocial media platforms (e.g., FACEBOOK®, INSTAGRAM®, LINKEDIN®,PINTEREST®, QZONE®, SNAPCHAT®, TWITTER®, VKontakte (VK), etc.). Forexample, each merchant may input one or more social media accountidentifiers (e.g., username and password) into loyalty portal 1040 toenable access and communication between loyalty portal 1040 and thesocial media platform. In that respect, and as discussed further herein,merchants may interact with each other via the one or more social mediaplatforms to form multi-merchant partnerships, as discussed furtherherein.

Loyalty portal 1040 may comprise a local contract repository. The localcontract repository may comprise any suitable database, data structure,file, or the like configured to store and maintain various partnershipsmart contract templates. In that regard, one or more loyalty partnersmay access loyalty portal 1040 to retrieve partnership smart contracttemplates. The loyalty partner may input various partnership parametersinto the partnership smart contract template, as discussed furtherherein, to generate a partnership smart contract. The partnership smartcontract may control the end-to-end data flow in loyalty point network100 and may autonomously govern the multi-merchant loyalty pointpartnership by supporting execution and recording of various data, asdiscussed further herein. The partnership smart contract may compriseexecutables that write data to blockchain 102 in a predetermined formatbased on predetermined function parameters passed by an API call or thelike, as discussed further herein. For example, the partnership smartcontract may include a program written in a programming language suchas, for example, Solidity, or any other suitable smart contractprogramming language.

Loyalty portal 1040 may comprise a local partner repository. The localpartner repository may comprise any suitable database, data, structure,file, or the like configured to store and maintain data regardingloyalty partners participating in multi-merchant partnerships (e.g.,participant data). The participant data may comprise data correspondingto each local partner, including partner characteristics, partnerpreferences, or the like. For example, partner characteristics maycomprise the partner identifier, the partner industry category, thepartner industry subcategory, a partner reputation, the partner history,the partner geographic, the partner goods or services sold, or the like.The partner preferences may comprise data regarding partnerships theloyalty partner desires to join, such as, for example, the type ofpurchase reward (e.g., partner discount, loyalty point payout, loyaltypartner credit, etc.), the partnership duration, the purchase amount, orthe like. The participant data may be grouped by each partner identifierin the local partner repository.

In various embodiments, loyalty portal 1040 may also comprise areputation ledger. The reputation ledger may comprise any suitabledatabase, data, structure, file, or the like configured to store andmaintain reputation data regarding one or more loyalty partners. Thereputation data may be generated based on merchant reviews, customerreviews, or the like, and may comprise a reputation score having anysuitable scale. In that respect, merchants may access loyalty portal1040 and may review or rate one or more other merchants in loyalty pointnetwork 100. In various embodiments, the reputation ledger may also bestored and maintained on blockchain 102, using any suitable techniquediscussed herein.

In various embodiments, loyalty point network 100 may comprise a banksettlement system 1020. Bank settlement system 1020 may be configured toauthorize and settle various transactions in loyalty point network 100.Bank settlement system 1020 may comprise any suitable combination ofhardware, software, and/or database components. For example, banksettlement system 1020 may comprise one or more network environments,servers, computer-based systems, processors, databases, and/or the like.Bank settlement system 1020 may comprise at least one computing devicein the form of a computer or processor, or a set of computers and/orprocessors, although other types of computing units or systems may beused, such as, for example, a server, web server, pooled servers, or thelike. Bank settlement system 1020 may also include one or more datacenters, cloud storages, or the like, and may include software, such asAPIs, configured to perform various operations discussed herein.

In various embodiments, bank settlement system 1020 may comprise orinteract with a traditional payment network or transaction network tofacilitate purchases and payments, authorize transactions, settletransactions, and the like. For example, bank settlement system 1020 mayrepresent existing proprietary networks that presently accommodatetransactions for credit cards, debit cards, and/or other types oftransaction accounts or transaction instruments. Bank settlement system1020 may be a closed network that is secure from eavesdroppers. Invarious embodiments, bank settlement system 1020 may comprise anexemplary transaction network such as AMERICAN EXPRESS®, VISANET®,MASTERCARD®, DISCOVER®, INTERAC®, Cartes Bancaires, JCB®, privatenetworks (e.g., department store networks), and/or any other paymentnetwork, transaction network, or the like. Bank settlement system 1020may include systems and databases related to financial and/ortransactional systems and processes, such as, for example, one or moreauthorization engines, authentication engines and databases, settlementengines and databases, accounts receivable systems and databases,accounts payable systems and databases, and/or the like. In variousembodiments, bank settlement system 1020 may also comprise a transactionaccount issuer's Credit Authorization System (“CAS”) capable ofauthorizing transactions, as discussed further herein.

Although the present disclosure makes reference to bank settlementsystem 1020, it should be understood that principles of the presentdisclosure may be applied to a system having any suitable number of banksettlement systems, issuer systems, payment networks, or the like. Forexample, loyalty point network 100 may comprise one or more banksettlement system 1020 each corresponding to or associated with adifferent issuer system or network.

In various embodiments, loyalty point network 100 may comprise anauditor 1030. Auditor 1030 may comprise any suitable combination ofhardware, software, and/or database components. For example, auditor1030 may comprise one or more network environments, servers,computer-based systems, processors, databases, and/or the like. Invarious embodiments, auditor 1030 may be computer based, and maycomprise a processor, a tangible non-transitory computer-readablememory, and/or a network interface, along with other suitable systemsoftware and hardware components. Instructions stored on the tangiblenon-transitory memory may allow auditor 1030 to perform variousfunctions, as described herein. The processor may include any logicdevice such as one or more of a central processing unit (CPU), anaccelerated processing unit (APU), a digital signal processor (DSP), afield programmable gate array (FPGA), an application specific integratedcircuit (ASIC), or the like.

Auditor 1030 may comprise software, a mobile application, a webinterface, or the like. For example, auditor 1030 may include agraphical user interface (“GUI”), software modules, logic engines,interfaces to systems and tools, and/or the like. Auditor 1030 may beconfigured to enable one or more third parties, systems, or the likeaccess to loyalty point network 100 to review and audit themulti-merchant partnerships, loyalty point distributions, and the like.For example, auditor 1030 may be granted read-only access to any desiredamount of transactions in loyalty point network 100, as well as currentbalances (e.g., loyalty partner balances, user balances, etc.) and thestate of relationships between loyalty partners.

Referring now to FIGS. 11-13 the process flows depicted are merelyembodiments and are not intended to limit the scope of the disclosure.For example, the steps recited in any of the method or processdescriptions may be executed in any order and are not limited to theorder presented. It will be appreciated that the following descriptionmakes appropriate references not only to the steps depicted in FIGS.11-13, but also to the various system components as described above withreference to FIG. 10. It should be understood at the outset that,although exemplary embodiments are illustrated in the figures anddescribed below, the principles of the present disclosure may beimplemented using any number of techniques, whether currently known ornot. The present disclosure should in no way be limited to the exemplaryimplementations and techniques illustrated in the figures and describedbelow.

With specific reference to FIG. 11, and in accordance with variousembodiments, a process 1100 for generating a multi-merchant loyaltypoint partnership arrangement is disclosed. A loyalty partner (e.g., afirst merchant) may generate the multi-merchant loyalty pointpartnership construct to specify various desired parameters of thepartnership, as discussed further herein. The loyalty partner maypreregister with the system as a loyalty coalition member (e.g., process700, with brief reference to FIG. 7). In various embodiments, themulti-merchant loyalty point partnership construct may comprise a smartcontract (e.g., a partnership smart contract) configured to controlend-to-end data flows (or any portion thereof) in the system based onthe various specified parameters.

In various embodiments, the loyalty partner (e.g., via loyalty partnersite 106) accesses loyalty portal 1040 (Step 1101). Access to loyaltyportal 1040 may be controlled using any suitable access control, suchas, for example, loyalty partner credentials (e.g., username, password,biometric input, etc.), one time passwords, or the like. The loyaltypartner may access loyalty portal 1040 to initiate the generation of apartnership smart contract (e.g., by interacting with a user interface(UI)). For example, the loyalty partner may initiate the generation ofthe partnership smart contract by selecting and/or inputting variousdesired partnership parameters such as, for example, the number ofpartners in the partnership (e.g., an exact number, a minimum number, amaximum number, a varying number based on certain factors, etc.),desired partnership industries (e.g., travel, hotel, etc.), or the like.In response to the loyalty partner initiating the generation, loyaltyportal 1040 retrieves a partnership smart contract template (Step 1102)from the local contract repository. Loyalty portal 1040 returns thepartnership smart contract template (Step 1103) to the loyalty partner(e.g., via loyalty partner site 106).

In response to receiving the partnership smart contract template, theloyalty partner may input and/or select various partnership parametersto be included in the partnership smart contract. For example,partnership parameters may include qualifying participant parameters,purchase requirement parameters, SKU-based rewards (as set forthherein), purchase reward parameters, partnership duration parameters, orthe like. The qualifying participant parameters may comprise datacorresponding to desired loyalty partner participants such as, forexample, a partner identifier (e.g., blockchain address, ID, etc.), apartner industry category (e.g., travel), a partner industry subcategory(e.g., hotel), a partner reputation requirement (e.g., based on areputation ledger, YELP® reviews, GOOGLE® reviews, a Better BusinessBureau (BBB®) accreditation, etc.), a partner history (e.g., length ofexistence in loyalty point network 100, length of loyalty partnerbusiness existence, etc.), a partner geographic location (e.g., UnitedStates, New York, N.Y. City, etc.), or the like. The purchaserequirement parameters may comprise data corresponding to the goods orservices that need to be purchased at each loyalty partner to completeat least a portion of the partnership smart contract. The purchaserequirement parameters may define the purchase requirements for eachindividual loyalty partner in the partnership, or may define collectiverequirements (a subset or all of the partners). For example, thepurchase requirement parameters may comprise a good or service type, ageographic restriction (e.g., all purchases must be completed within NewYork City), a purchase amount (e.g., a minimum purchase amount), or thelike. The purchase reward parameters may define the payout or reward acustomer earns in response to completing the partnership smart contract.For example, the purchase reward parameters may comprise a partnerdiscount (e.g., a future discount at one or more of the loyaltypartners, a retroactive discount at one or more of the loyalty partners,etc.), a loyalty point payout (e.g., 500 loyalty points), a loyaltypartner credit (e.g., a credit applied to the customer's transactionaccount), or the like. The partnership duration parameter may define theduration of the partnership smart contract, such as, for example, a timeperiod, an expiration date, a maximum number of completed contracts, orthe like.

The various partnership parameters may be input into the partnershipsmart contract template to generate the partnership smart contract. Invarious embodiments, the loyalty partner requests creation of thepartnership smart contract with blockchain API host 104 (Step 1104). Forexample, the loyalty partner (via loyalty partner site 106) may invokeblockchain API host 104 by transmitting the partnership smart contractto blockchain API host 104. In response to being invoked, blockchain APIhost 104 propagates the partnership smart contract to consensusparticipants 103 (Step 1105) by transmitting the partnership smartcontract to consensus participants 103 and/or by writing the partnershipsmart contract to blockchain 102. In various embodiments, thepartnership smart contract write may also comprise data regarding theloyalty partner (e.g., as the first loyalty partner in the partnership),such as, for example, a partner identifier or the like.

Consensus participants 103 achieve consensus and add the partnershipsmart contract to blockchain 102 (Step 1106). Consensus participants 103may achieve consensus using proof of work, proof of stake, practicalbyzantine fault tolerance, delegated proof of stake, or other suitableconsensus algorithm. Consensus participants 103 may write thepartnership smart contract to blockchain 102 using any suitabletechnique. In response to achieving consensus and completing the write,consensus participants 103 transmit a write confirmation to blockchainAPI host 104 (Step 1107). The write confirmation may comprise dataindicating that the partnership smart contract was successfully writtento blockchain 102. In various embodiments, the write confirmation mayalso comprise data pointing to the location of the write on blockchain102, such as a uniform resource locator (URL), or the like. In responseto receiving the write confirmation, blockchain API host 104 transmitsthe write confirmation to the loyalty partner (Step 1108), such as, forexample, via loyalty partner site 106.

The loyalty partner (e.g., via loyalty partner site 106) requestsparticipant notification with loyalty portal 1040 (Step 1109), based onthe partnership parameters of the partnership smart contract. Forexample, the loyalty partner, via loyalty partner site 106, may transmitthe partnership parameters and/or the partnership smart contract toloyalty portal 1040. Loyalty portal 1040 retrieves qualifyingparticipant data from local partner repository (Step 1110), based on thepartnership parameters and/or the partnership smart contract. Forexample, the local partner repository may store participant data foreach loyalty partner in the system. The participant data may comprisedata corresponding to each local partner, including partnercharacteristics, partner preferences, or the like. For example, partnercharacteristics may comprise the partner identifier, the partnerindustry category, the partner industry subcategory, a partnerreputation, the partner history, the partner geographic, the partnergoods or services sold, or the like. The partner preferences maycomprise data regarding partnerships the loyalty partner desires tojoin, such as, for example, the type of purchase reward (e.g., partnerdiscount, loyalty point payout, loyalty partner credit, etc.), thepartnership duration, the purchase amount, or the like. The participantdata may be grouped by each partner identifier.

In that regard, loyalty portal 1040 may locate one or more loyaltypartners comprising participant data that at least partially matches thepartnership parameters. Loyalty portal 1040 broadcasts a partnershipnotification to qualifying participants (Step 1111). The partnershipnotification may comprise data corresponding to the partnership smartcontract, such as, for example, a blockchain URL (e.g., the location ofthe partnership smart contract in blockchain 102), the partnershipparameters, or the like. In various embodiments, loyalty portal 1040 mayalso broadcast the partnership notification to all participants in thesystem.

With specific reference to FIG. 12, and in accordance with variousembodiments, a process 1200 for enrolling a partner in a multi-merchantloyalty point partnership is disclosed. A loyalty partner may desire toenroll in one or more multi-merchant loyalty point partnership. Theloyalty partner (e.g., via loyalty partner site 106) requests activepartnership smart contracts from loyalty portal 1040 (Step 1201). Forexample, the loyalty partner may request one or more active partnershipsmart contracts in response to receiving the partnership notification inStep 1111. As a further example, the loyalty partner may request theactive partnership smart contracts to browse and review variousavailable and active partnership smart contracts. In that regard, therequest may comprise a request for a specific partnership smart contract(e.g., based on the blockchain URL) or a general request for one or moreactive partnership smart contracts.

In response to receiving the request, loyalty portal 1040 retrievespartner data from local partner repository (Step 1202) corresponding tothe loyalty partner. For example, loyalty portal 1040 may retrieve thepartner data based on the partner identifier. Loyalty portal 1040invokes blockchain API host 104 (Step 1204) to return qualifying activepartnership smart contracts. For example, loyalty portal 1040 may invokeblockchain API host 104 by transmitting the partner data to blockchainAPI host 104. In various embodiments, loyalty portal 1040 may alsoinvoke blockchain API host 104 by transmitting the blockchain URL. Inresponse to being invoked, blockchain API host 104 retrieves and returnsqualifying active partnership smart contracts to the loyalty partner(e.g., via loyalty partner site 106) (Step 1205).

In that regard, and in accordance with various embodiments, blockchainAPI host 104 may retrieve the specific partnership smart contract basedon the blockchain URL. In various embodiments, blockchain API host 104may also retrieve one or more active partnership smart contracts basedon the partner data. For example, blockchain API host 104 may retrievepartnership smart contracts having partnership parameters that at leastpartially match the partner data retrieved in Step 1202. Blockchain APIhost 104 may return the one or more partnership smart contracts to theloyalty partner, via loyalty partner site 106.

In response to receiving the partnership smart contracts, the loyaltypartner may review the partnership smart contracts to determine whetherthe loyalty partner desires to enroll in one or more partnership smartcontracts. The loyalty partner (e.g., via loyalty partner site 106)invokes blockchain API host 104 by transmitting a partnership enrollmentrequest (Step 1206). The partnership enrollment request may comprisedata indicating the partnership smart contract that the loyalty partnerdesires to enroll in (e.g., by blockchain URL, smart contract ID, etc.),partner data (e.g., a partner identifier, etc.), or the like. Inresponse to being invoked, blockchain API host 104 propagates thepartnership enrollment request to consensus participants 103 (Step 1207)by transmitting the partnership enrollment request to consensusparticipants 103 and/or by writing the enrollment request to blockchain102.

Consensus participants 103 achieve consensus and add the enrollmentrequest to blockchain 102 (Step 1208). Consensus participants 103 mayachieve consensus using proof of work, proof of stake, practicalbyzantine fault tolerance, delegated proof of stake, or other suitableconsensus algorithm. Consensus participants 103 may write thepartnership smart contract to blockchain 102 using any suitabletechnique. In response to achieving consensus and completing the write,consensus participants 103 transmit an update write confirmation toblockchain API host 104 (Step 1209).

In response to the partnership smart contract completing loyalty partnerenrollment (e.g., in response to the specified number of partners in thepartnership being met), the partnership smart contract may mark thepartnership as active.

With specific reference to FIG. 13, and in accordance with variousembodiments, a process 1300 for customer-completion of a multi-merchantloyalty point partnership is disclosed. In various embodiments, customer109 may be aware of the loyalty point partnership prior to shopping atthe loyalty partners. For example, the loyalty point partnership may beadvertised, customer 109 may be directly notified, or the like. Invarious embodiments, customer 109 may be unaware of the loyalty pointpartnership prior to shopping at the loyalty partners. In that regard,customer 109 may still receive the purchase reward (e.g., partnerdiscount, loyalty point payout, loyalty partner credit, etc.), inresponse to completing the requirements of the loyalty pointpartnership.

Customer 109 shops with a first loyalty partner by browsing loyaltypartner site 106A (Step 1301). For example, customer 109 may browseloyalty partner site to select one or more products or services. Loyaltypartner site 106A retrieves product data (Step 1302) based on customer109 selections. Customer 109 may continue to select product and/orservices, or may proceed with the checkout process. In response tocustomer 109 initiating the checkout process, loyalty partner site 106Amay prompt customer 109 to select a payment method, such as, forexample, using a transaction account, customer loyalty points, giftcards, or any other suitable payment type. In response to customer 109selecting loyalty points, loyalty partner site 106A prompts customer109, and/or loyalty wallet 105, for the corresponding loyalty account atcheckout (Step 1303). The loyalty account may be identifiable by auniversally unique identifier (UUID), for example. Customer 109 providesthe loyalty account (Step 1304) in response to the prompt by enteringthe loyalty account and/or by loyalty wallet 105 transmitting theloyalty account. Customer 109 may also input or select various paymentinformation and preferences, such as, for example, shipping information,billing information, or the like. In response to customer 109 inputtingand/or selecting various payment preferences, loyalty partner site 106Amay communicate with bank settlement system 1020 to authorize, settle,and/or complete the transaction.

In response to completing the purchase, loyalty partner site 106Ainvokes blockchain API host 104 (step 1305) by transmitting the loyaltyaccount and/or transaction data (e.g., products or services purchased,transaction total, etc.). In various embodiments, access to blockchainAPI host 104 may be provided to each loyalty partner by an independentcloud service provider offering blockchain as a service (BaaS)functionality (e.g., via a paid service subscription or the like). Inresponse to being invoked, blockchain API host 104 executes the partnersmart contract. The partner smart contract may validate whether thetransaction data from the completed purchase meets the variouspartnership parameters. In response to the transaction data qualifying,the partner smart contract records the transaction (step 1306). Forexample, the partner smart contract records the loyalty account, and atag, note, or the like indicating that a qualifying purchase wascompleted with the loyalty account. In response to customer 109selecting to at least partially complete the purchase using loyaltypoints, partner smart contract may also adjust the loyalty point balance(see step 305 of FIG. 3).

Blockchain API host 104 propagates the transaction record write toconsensus participants 103 by transmitting the transaction record writeto consensus participants 103 and/or by writing the transaction recordwrite to blockchain 102 (step 1307). Consensus participants 103 achieveconsensus and add the transaction record to the blockchain 102 (Step1308). Consensus participants 103 may achieve consensus using proof ofwork, proof of stake, practical byzantine fault tolerance, delegatedproof of stake, or other suitable consensus algorithm. Consensusparticipants 103 may write the transaction record to blockchain 102using any suitable technique. In response to achieving consensus andcompleting the write, consensus participants 103 transmit a transactionrecord confirmation to blockchain API host 104 (step 1309). Thetransaction record confirmation may comprise data indicating that thetransaction record was successfully written to blockchain 102. Invarious embodiments, the transaction record confirmation may alsocomprise data pointing to the location of the write on blockchain 102,such as a uniform resource locator (URL), or the like. Consensusparticipants 103 may also notify customer 109 of the completed loyaltypoint balance adjustment.

In various embodiments, customer 109 shops with a second loyalty partnerby browsing loyalty partner site 106B (Step 1310). The second loyaltypartner may be a second partner in the partnership smart contract. Forexample, customer 109 may browse loyalty partner site 106B to select oneor more products or services. Loyalty partner site 106B retrievesproduct data (step 1311) based on customer 109 selections. Customer 109may continue to select product and/or services, or may proceed with thecheckout process. In response to customer 109 initiating the checkoutprocess, loyalty partner site 106B may prompt customer 109 to select apayment method, such as, for example, using a transaction account,customer loyalty points, gift cards, or any other suitable payment type.In response to customer 109 selecting loyalty points, loyalty partnersite 106B prompts customer 109, and/or loyalty wallet 105, for thecorresponding loyalty account at checkout (Step 1312). Customer 109provides the loyalty account (Step 1313) in response to the prompt byentering the loyalty account and/or by loyalty wallet 105 transmittingthe loyalty account. Customer 109 may also input or select variouspayment information and preferences, such as, for example, shippinginformation, billing information, or the like. In response to customer109 inputting and/or selecting various payment preferences, loyaltypartner site 106B may communicate with bank settlement system 1020 toauthorize, settle, and/or complete the transaction.

In response to completing the purchase, loyalty partner site 106Binvokes blockchain API host 104 (Step 1314) by transmitting the loyaltyaccount and/or transaction data (e.g., products or services purchased,transaction total, etc.). In response to being invoked, blockchain APIhost 104 executes the partner smart contract. The partner smart contractmay validate whether the transaction data from the completed purchasemeets the various partnership parameters. In response to the transactiondata qualifying, the partner smart contract records the transaction(step 1315). For example, the partner smart contract records the loyaltyaccount, and a tag, note, or the like indicating that a qualifyingpurchase was completed with the loyalty account. In response to customer109 selecting to at least partially complete the purchase using loyaltypoints, partner smart contract may also adjust the loyalty point balance(see step 305 of FIG. 3). Consensus participants 103 may also notifycustomer 109 of the completed loyalty point balance adjustment.

Blockchain API host 104 propagates the transaction record write toconsensus participants 103 by transmitting the transaction record writeto consensus participants 103 and/or by writing the transaction recordwrite to blockchain 102 (Step 1316). Consensus participants 103 achieveconsensus and add the transaction record to the blockchain 102 (Step1317). Consensus participants 103 may achieve consensus using proof ofwork, proof of stake, practical byzantine fault tolerance, delegatedproof of stake, or other suitable consensus algorithm. Consensusparticipants 103 may write the transaction record to blockchain 102using any suitable technique. In response to achieving consensus andcompleting the write, consensus participants 103 transmit a transactionrecord confirmation to blockchain API host 104 (step 1318). Thetransaction record confirmation may comprise data indicating that thetransaction record was successfully written to blockchain 102. Invarious embodiments, the transaction record confirmation may alsocomprise data pointing to the location of the write on blockchain 102,such as a uniform resource locator (URL), or the like. Consensusparticipants 103 may also notify customer 109 of the completed loyaltypoint balance adjustment.

In various embodiments, in response to receiving the transaction recordconfirmation, blockchain API host 104 may execute the partner smartcontract to update the loyalty account corresponding to customer 109 inthe partnership smart contract. The partner smart contract may determinethat customer 109 has completed the requirements of the partnershipparameters, such as, for example in response to customer 109 completinga qualifying purchase at each of the loyalty partners partnered in thepartner smart contract. In response to the purchase reward being aloyalty point payout, blockchain API host 104 may adjust the loyaltypoint balance of customer 109 using any suitable technique, such as, forexample using process 300, with brief reference to FIG. 3. BlockchainAPI host 104 transmits the transaction record confirmation and/or apartnership completion notification to loyalty partner site 106B (Step1319). The partnership completion notification may comprise datacorresponding to the purchase reward, and/or any other suitable dataregarding the completion of the partnership.

Loyalty partner site 106B notifies customer 109 of completion of themulti-merchant loyalty point partnership (Step 1320). In response to thepurchase reward being the loyalty point payout, the customernotification may also comprise the loyalty point payout amount and thecompleted balance adjustment. In response to the purchase reward being apartner discount or a loyalty partner credit, the customer notificationmay comprise data indicating the amount of the partner discount or theloyalty partner credit.

In various embodiments, auditor 1030 may be granted access to blockchain102 (and/or to an audit log of writes to blockchain 102). Auditor 1030may be configured to access and retrieve the writes, such as, forexample, by migrating the data to a dedicating audit database. Auditor1030 may perform various analytical processing on the data as requiredby desired or suitable auditing needs.

The systems and processes described herein improve the functioning ofthe computer by propagating loyalty point data quickly and immutably,and enabling multi-merchant loyalty point partnerships. For example, bythe user may simply request a transaction using stored blockchain keysand account numbers as opposed to manually inputting data, the userperforms less computer functions and provides less input, which saves ondata storage and memory which speeds processing. Additionally, bytransmitting, storing, and accessing data using the processes describedherein, the security of the data is improved, which decreases the riskof the computer or network from being compromised. Use of blockchain 102ensures integrity and immutability of communications in such way thatneither of the interacting parties have to rely on a specific entity tomaintain the state of the ledger. The use of blockchain 102 may alsoenable full transparency. Since all participants in effect maintain asingle ledger, consistency may be maintained between various blockchainnodes. The complexity of the system is also reduced by alleviating theuse of offline and/or batch processes typically used to keep multiplesystems in sync. Further, by syncing data with the involved parties inreal time (or near real time), the system may improve data integrity,data confidentiality, and data security, which may also improve thespeed of the business process. The system may also reduce databasesynchronization errors by providing a common data structure, thus atleast partially improving the integrity of stored data.

Data transfers performed through the system may propagate to theconnected peers within the blockchain network within a duration that maybe determined by the block creation time of the specific blockchaintechnology implemented. For example, on an ETHEREUM®-based network, anew data entry may become available within about 13-20 seconds as of thewriting. On a HYPERLEDGER® Fabric 1.0 based platform, the duration isdriven by the specific consensus algorithm that is chosen, and may beperformed within seconds. In that respect, propagation times and thespeed of transferring data, initiating purchases, and completingpurchases in the system may be improved compared to existing systems,and implementation costs and time to market may also be drasticallyreduced.

In various embodiments, the system also offers increased reliability andfault tolerance over traditional databases (e.g., relational databases,distributed databases, etc.) as each node may operate with a full copyof the stored data, thus at least partially reducing downtime due tolocalized network outages and hardware failures. The system may alsoincrease the reliability of data transfers in a network environmenthaving reliable and unreliable peers, as each node broadcasts messagesto all connected peers, and, as each block comprises a link to aprevious block, a node may quickly detect a missing block and propagatea request for the missing block to the other nodes in the blockchainnetwork. For more information on distributed ledgers implementingfeatures and functionalities of blockchain, see U.S. application Ser.No. 15/266,350 titled SYSTEMS AND METHODS FOR BLOCKCHAIN BASED PAYMENTNETWORKS and filed on Sep. 15, 2016, U.S. application Ser. No.15/682,180 titled SYSTEMS AND METHODS FOR DATA FILE TRANSFER BALANCINGAND CONTROL ON BLOCKCHAIN and filed Aug. 21, 2017, U.S. application Ser.No. 15/785,843 titled MESSAGING BALANCING AND CONTROL ON BLOCKCHAIN andfiled on Oct. 17, 2017, U.S. application Ser. No. 15/785,870 titled APIREQUEST AND RESPONSE BALANCING AND CONTROL ON BLOCKCHAIN and filed onOct. 17, 2017, U.S. application Ser. No. 15/824,450 titled SINGLESIGN-ON SOLUTION USING BLOCKCHAIN and filed on Nov. 28, 2017, U.S.application Ser. No. 15/824,513 titled TRANSACTION AUTHORIZATION PROCESSUSING BLOCKCHAIN and filed on Nov. 28, 2017, and U.S. application Ser.No. 16/012,598 titled BUYER-CENTRIC MARKETPLACE USING BLOCKCHAIN andfiled on Jun. 19, 2018, the contents of which are each incorporated byreference in its entirety.

Systems, methods, and computer program products are provided. In thedetailed description herein, references to “various embodiments,” “oneembodiment,” “an embodiment,” “an example embodiment,” etc., indicatethat the embodiment described may include a particular feature,structure, or characteristic, but every embodiment may not necessarilyinclude the particular feature, structure, or characteristic. Moreover,such phrases are not necessarily referring to the same embodiment.Further, when a particular feature, structure, or characteristic isdescribed in connection with an embodiment, it is submitted that it iswithin the knowledge of one skilled in the art to affect such feature,structure, or characteristic in connection with other embodimentswhether or not explicitly described. After reading the description, itwill be apparent to one skilled in the relevant art(s) how to implementthe disclosure in alternative embodiments.

As used herein, “satisfy,” “meet,” “match,” “associated with”, orsimilar phrases may include an identical match, a partial match, meetingcertain criteria, matching a subset of data, a correlation, satisfyingcertain criteria, a correspondence, an association, an algorithmicrelationship, and/or the like. Similarly, as used herein, “authenticate”or similar terms may include an exact authentication, a partialauthentication, authenticating a subset of data, a correspondence,satisfying certain criteria, an association, an algorithmicrelationship, and/or the like.

Terms and phrases similar to “associate” and/or “associating” mayinclude tagging, flagging, correlating, using a look-up table or anyother method or system for indicating or creating a relationship betweenelements, such as, for example, (i) a transaction account and (ii) anitem (e.g., offer, reward, discount, etc.) and/or digital channel.Moreover, the associating may occur at any point, in response to anysuitable action, event, or period of time. The associating may occur atpre-determined intervals, periodic, randomly, once, more than once, orin response to a suitable request or action. Any of the information maybe distributed and/or accessed via a software enabled link, wherein thelink may be sent via an email, text, post, social network input, and/orany other method known in the art.

Phrases and terms similar to “account,” “account number,” “accountcode,” or “consumer account” as used herein, may include any device,code (e.g., one or more of an authorization/access code, personalidentification number (“PIN”), Internet code, other identification code,and/or the like), number, letter, symbol, digital certificate, smartchip, digital signal, analog signal, biometric or otheridentifier/indicia suitably configured to allow the consumer to access,interact with or communicate with the system. The account number mayoptionally be located on or associated with a rewards account, chargeaccount, credit account, debit account, prepaid account, telephone card,embossed card, smart card, magnetic stripe card, bar code card,transponder, radio frequency card or an associated account.

The phrases “consumer,” “customer,” “user,” “account holder,” “accountaffiliate,” “cardmember,” or the like shall include any person, entity,business, government organization, business, software, hardware, machineassociated with a transaction account, buys merchant offerings offeredby one or more merchants using the account and/or who is legallydesignated for performing transactions on the account, regardless ofwhether a physical card is associated with the account. For example, thecardmember may include a transaction account owner, a transactionaccount user, an account affiliate, a child account user, a subsidiaryaccount user, a beneficiary of an account, a custodian of an account,and/or any other person or entity affiliated or associated with atransaction account.

In various embodiments, the methods described herein are implementedusing the various particular machines described herein. The methodsdescribed herein may be implemented using the below particular machines,and those hereinafter developed, in any suitable combination, as wouldbe appreciated immediately by one skilled in the art. Further, as isunambiguous from this disclosure, the methods described herein mayresult in various transformations of certain articles.

The various system components discussed herein may include one or moreof the following: a host server or other computing systems including aprocessor for processing digital data; a memory coupled to the processorfor storing digital data; an input digitizer coupled to the processorfor inputting digital data; an application program stored in the memoryand accessible by the processor for directing processing of digital databy the processor; a display device coupled to the processor and memoryfor displaying information derived from digital data processed by theprocessor; and a plurality of databases. Various databases used hereinmay include: client data; merchant data; financial institution data;and/or like data useful in the operation of the system. As those skilledin the art will appreciate, user computer may include an operatingsystem (e.g., WINDOWS®, UNIX®, LINUX®, SOLARIS®, MACOS®, etc.) as wellas various conventional support software and drivers typicallyassociated with computers.

The present system, or any part(s) or function(s) thereof, may beimplemented using hardware, software, or a combination thereof and maybe implemented in one or more computer systems or other processingsystems. However, the manipulations performed by embodiments were oftenreferred to in terms, such as matching or selecting, which are commonlyassociated with mental operations performed by a human operator. No suchcapability of a human operator is necessary, or desirable in most cases,in any of the operations described herein. Rather, the operations may bemachine operations or any of the operations may be conducted or enhancedby artificial intelligence (AI) or machine learning. Artificialintelligence may refer generally to the study of agents (e.g., machines,computer-based systems, etc.) that perceive the world around them, formplans, and make decisions to achieve their goals. Foundations of AIinclude mathematics, logic, philosophy, probability, linguistics,neuroscience, and decision theory. Many fields fall under the umbrellaof AI, such as computer vision, robotics, machine learning, and naturallanguage processing. Useful machines for performing the variousembodiments include general purpose digital computers or similardevices.

In various embodiments, the embodiments are directed toward one or morecomputer systems capable of carrying out the functionalities describedherein. The computer system includes one or more processors. Theprocessor is connected to a communication infrastructure (e.g., acommunications bus, cross over bar, network, etc.). Various softwareembodiments are described in terms of this exemplary computer system.After reading this description, it will become apparent to a personskilled in the relevant art(s) how to implement various embodimentsusing other computer systems and/or architectures. The computer systemcan include a display interface that forwards graphics, text, and otherdata from the communication infrastructure (or from a frame buffer notshown) for display on a display unit.

The computer system also includes a main memory, such as random accessmemory (RAM), and may also include a secondary memory. The secondarymemory may include, for example, a hard disk drive, a solid-state drive,and/or a removable storage drive. The removable storage drive reads fromand/or writes to a removable storage unit in a well-known manner. Aswill be appreciated, the removable storage unit includes a computerusable storage medium having stored therein computer software and/ordata.

In various embodiments, secondary memory may include other similardevices for allowing computer programs or other instructions to beloaded into a computer system. Such devices may include, for example, aremovable storage unit and an interface. Examples of such may include aprogram cartridge and cartridge interface (such as that found in videogame devices), a removable memory chip (such as an erasable programmableread only memory (EPROM), programmable read only memory (PROM)) andassociated socket, or other removable storage units and interfaces,which allow software and data to be transferred from the removablestorage unit to a computer system.

The terms “computer program medium,” “computer usable medium,” and“computer readable medium” are used to generally refer to media such asremovable storage drive and a hard disk installed in hard disk drive.These computer program products provide software to a computer system.

The computer system may also include a communications interface. Acommunications interface allows software and data to be transferredbetween the computer system and external devices. Examples ofcommunications interface may include a modem, a network interface (suchas an Ethernet card), a communications port, a Personal Computer MemoryCard International Association (PCMCIA) slot and card, etc. Software anddata transferred via the communications interface are in the form ofsignals which may be electronic, electromagnetic, optical, or othersignals capable of being received by communications interface. Thesesignals are provided to communications interface via a communicationspath (e.g., channel). This channel carries signals and may beimplemented using wire, cable, fiber optics, a telephone line, acellular link, a radio frequency (RF) link, wireless and othercommunications channels.

Any communication, transmission, communications channel, channel, and/orthe like discussed herein may include any system or method fordelivering content (e.g. data, information, metadata, etc.), and/or thecontent itself. The content may be presented in any form or medium, andin various embodiments, the content may be delivered electronicallyand/or capable of being presented electronically. For example, a channelmay comprise a website, mobile application, or device (e.g., FACEBOOK®,YOUTUBE®, PANDORA®, APPLE TV®, MICROSOFT® XBOX®, ROKU®, AMAZON FIRE®,GOOGLE CHROMECAST™, SONY® PLAYSTATION®, NINTENDO® SWITCH®, etc.) auniform resource locator (“URL”), a document (e.g., a MICROSOFT® Word™or EXCEL®, an ADOBE® Portable Document Format (PDF) document, etc.), an“ebook,” an “emagazine,” an application or microapplication (asdescribed herein), an SMS or other type of text message, an email, aFACEBOOK® message, a TWITTER® tweet, multimedia messaging services(MMS), and/or other type of communication technology. In variousembodiments, a channel may be hosted or provided by a data partner. Invarious embodiments, the distribution channel may comprise at least oneof a merchant website, a social media website, affiliate or partnerwebsites, an external vendor, a mobile device communication, socialmedia network, and/or location based service. Distribution channels mayinclude at least one of a merchant website, a social media site,affiliate or partner websites, an external vendor, and a mobile devicecommunication. Examples of social media sites include FACEBOOK®,FOURSQUARE®, TWITTER®, LINKEDIN®, INSTAGRAM®, PINTEREST®, TUMBLR®,REDDIT®, SNAPCHAT®, WHATSAPP®, FLICKR®, VK®, QZONE®, WECHAT®, and thelike. Examples of affiliate or partner websites include AMERICANEXPRESS®, GROUPON®, LIVINGSOCIAL®, and the like. Moreover, examples ofmobile device communications include texting, email, and mobileapplications for smartphones.

Computer programs (also referred to as computer control logic) arestored in main memory and/or secondary memory. Computer programs mayalso be received via communications interface. Such computer programs,when executed, enable the computer system to perform the features asdiscussed herein. In particular, the computer programs, when executed,enable the processor to perform the features of various embodiments.Accordingly, such computer programs represent controllers of thecomputer system.

These computer program instructions may be loaded onto a general purposecomputer, special purpose computer, or other programmable dataprocessing apparatus to produce a machine, such that the instructionsthat execute on the computer or other programmable data processingapparatus create means for implementing the functions specified in theflowchart block or blocks. These computer program instructions may alsobe stored in a computer-readable memory that can direct a computer orother programmable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer-readablememory produce an article of manufacture including instruction meanswhich implement the function specified in the flowchart block or blocks.The computer program instructions may also be loaded onto a computer orother programmable data processing apparatus to cause a series ofoperational steps to be performed on the computer or other programmableapparatus to produce a computer-implemented process such that theinstructions which execute on the computer or other programmableapparatus provide steps for implementing the functions specified in theflowchart block or blocks.

Accordingly, functional blocks of the block diagrams and flowchartillustrations support combinations of means for performing the specifiedfunctions, combinations of steps for performing the specified functions,and program instruction means for performing the specified functions. Itwill also be understood that each functional block of the block diagramsand flowchart illustrations, and combinations of functional blocks inthe block diagrams and flowchart illustrations, can be implemented byeither special purpose hardware-based computer systems which perform thespecified functions or steps, or suitable combinations of specialpurpose hardware and computer instructions. Further, illustrations ofthe process flows and the descriptions thereof may make reference touser WINDOWS® applications, webpages, websites, web forms, prompts, etc.Practitioners will appreciate that the illustrated steps describedherein may comprise in any number of configurations including the use ofWINDOWS® applications, webpages, web forms, popup WINDOWS® applications,prompts, and the like. It should be further appreciated that themultiple steps as illustrated and described may be combined into singlewebpages and/or WINDOWS® applications but have been expanded for thesake of simplicity. In other cases, steps illustrated and described assingle process steps may be separated into multiple webpages and/orWINDOWS® applications but have been combined for simplicity.

In various embodiments, software may be stored in a computer programproduct and loaded into a computer system using removable storage drive,hard disk drive, or communications interface. The control logic(software), when executed by the processor, causes the processor toperform the functions of various embodiments as described herein. Invarious embodiments, hardware components may take the form ofapplication specific integrated circuits (ASICs). Implementation of thehardware state machine so as to perform the functions described hereinwill be apparent to persons skilled in the relevant art(s).

In various embodiments, components, modules, and/or engines of loyaltypoint network 100 may be implemented as micro-applications ormicro-apps. Micro-apps are typically deployed in the context of a mobileoperating system, including for example, a WINDOWS® mobile operatingsystem, an ANDROID® operating system, an APPLE® iOS operating system, aBLACKBERRY® company's operating system, and the like. The micro-app maybe configured to leverage the resources of the larger operating systemand associated hardware via a set of predetermined rules which governthe operations of various operating systems and hardware resources. Forexample, where a micro-app desires to communicate with a device ornetwork other than the mobile device or mobile operating system, themicro-app may leverage the communication protocol of the operatingsystem and associated device hardware under the predetermined rules ofthe mobile operating system. Moreover, where the micro-app desires aninput from a user, the micro-app may be configured to request a responsefrom the operating system which monitors various hardware components andthen communicates a detected input from the hardware to the micro-app.

In various embodiments, the system may implement middleware to providesoftware applications and services, and/or to bridge software componentsin the computer based system, such as the operating system, database,applications, and the like. Middleware may include any hardware and/orsoftware suitably configured to facilitate communications and/or processtransactions between disparate computing systems. Middleware componentsare commercially available and known in the art. Middleware may beimplemented through commercially available hardware and/or software,through custom hardware and/or software components, or through acombination thereof. Middleware may reside in a variety ofconfigurations and may exist as a standalone system or may be a softwarecomponent residing on the internet server. Middleware may be configuredto process transactions between the various components of an applicationserver and any number of internal or external systems for any of thepurposes disclosed herein. WEBSPHERE® MQ™ (formerly MQSeries) by IBM®,Inc. (Armonk, N.Y.) is an example of a commercially available middlewareproduct. An Enterprise Service Bus (“ESB”) application is anotherexample of middleware.

The systems, computers, computer based systems, and the like disclosedherein may provide a suitable website or other internet-based graphicaluser interface which is accessible by users. Practitioners willappreciate that there are a number of methods for displaying data withina browser-based document. Data may be represented as standard text orwithin a fixed list, scrollable list, drop-down list, editable textfield, fixed text field, pop-up window, and the like. Likewise, thereare a number of methods available for modifying data in a web page suchas, for example, free text entry using a keyboard, selection of menuitems, check boxes, option boxes, and the like.

Any of the communications, inputs, storage, databases or displaysdiscussed herein may be facilitated through a website having web pages.The term “web page” as it is used herein is not meant to limit the typeof documents and applications that might be used to interact with theuser. For example, a typical website might include, in addition tostandard HTML documents, various forms, JAVA® applets, JAVASCRIPT®programs, active server pages (ASP), common gateway interface scripts(CGI), extensible markup language (XML), dynamic HTML, cascading stylesheets (CSS), AJAX (Asynchronous JAVASCRIPT And XML) programs, helperapplications, plug-ins, and the like. A server may include a web servicethat receives a request from a web server, the request including a URLand an IP address (192.168.1.1). The web server retrieves theappropriate web pages and sends the data or applications for the webpages to the IP address. Web services are applications that are capableof interacting with other applications over a communications means, suchas the internet. Web services are typically based on standards orprotocols such as XML, SOAP, AJAX, WSDL and UDDI. Web services methodsare well known in the art, and are covered in many standard texts. As afurther example, representational state transfer (REST), or RESTful, webservices may provide one way of enabling interoperability betweenapplications.

In one embodiment, MICROSOFT® company's Internet Information Services(IIS), Transaction Server (MTS) service, and an SQL SERVER® database,are used in conjunction with MICROSOFT® operating systems, WINDOWS NT®web server software, SQL SERVER® database, and MICROSOFT′ CommerceServer. Additionally, components such as ACCESS® software, SQL SERVER®database, ORACLE® software, SYBASE® software, INFORMIX® software, MYSQL®software, INTERBASE® software, etc., may be used to provide an ActiveData Object (ADO) compliant database management system. In oneembodiment, the APACHE® web server is used in conjunction with a LINUX®operating system, a MYSQL® database, and PERL®, PHP, Ruby, and/orPYTHON® programming languages.

In various embodiments, the server may include application servers (e.g.WEBSPHERE®, WEBLOGIC®, JBOSS®, POSTGRES PLUS ADVANCED SERVER®, etc.). Invarious embodiments, the server may include web servers (e.g. Apache,IIS, GOOGLE® Web Server, SUN JAVA® System Web Server, JAVA® VirtualMachine running on LINUX® or WINDOWS' operating systems).

Users, systems, computer based systems or the like may communicate withthe server via a web client. The web client includes any device orsoftware which communicates via any network, such as, for example anydevice or software discussed herein. The web client may include internetbrowsing software installed within a computing unit or system to conductonline transactions and/or communications. These computing units orsystems may take the form of a computer or set of computers, althoughother types of computing units or systems may be used, includingpersonal computers, laptops, notebooks, tablets, smart phones, cellularphones, personal digital assistants, servers, pooled servers, mainframecomputers, distributed computing clusters, kiosks, terminals, point ofsale (POS) devices or terminals, televisions, or any other devicecapable of receiving data over a network. The web client may include anoperating system (e.g., WINDOWS®, WINDOWS MOBILE® operating systems,UNIX® operating system, LINUX® operating systems, APPLE® OS® operatingsystems, etc.) as well as various conventional support software anddrivers typically associated with computers. The web-client may also runMICROSOFT® INTERNET EXPLORER® software, MOZILLA® FIREFOX® software,GOOGLE® CHROME® software, APPLE® SAFARI® software, or any other of themyriad software packages available for browsing the internet.

As those skilled in the art will appreciate, the web client may or maynot be in direct contact with the server (e.g., application server, webserver, etc., as discussed herein). For example, the web client mayaccess the services of the server through another server and/or hardwarecomponent, which may have a direct or indirect connection to an internetserver. For example, the web client may communicate with the server viaa load balancer. In various embodiments, web client access is through anetwork or the internet through a commercially-available web-browsersoftware package. In that regard, the web client may be in a home orbusiness environment with access to the network or the internet. The webclient may implement security protocols such as Secure Sockets Layer(SSL) and Transport Layer Security (TLS). A web client may implementseveral application layer protocols including HTTP, HTTPS, FTP, andSFTP.

Any database discussed herein may include relational, hierarchical,graphical, blockchain, object-oriented structure, and/or any otherdatabase configurations. Any database may also include a flat filestructure wherein data may be stored in a single file in the form ofrows and columns, with no structure for indexing and no structuralrelationships between records. For example, a flat file structure mayinclude a delimited text file, a CSV (comma-separated values) file,and/or any other suitable flat file structure. Common database productsthat may be used to implement the databases include DB2® by IBM®(Armonk, N.Y.), various database products available from ORACLE®Corporation (Redwood Shores, Calif.), MICROSOFT ACCESS® or MICROSOFT SQLSERVER® by MICROSOFT® Corporation (Redmond, Wash.), MYSQL® by MySQL AB(Uppsala, Sweden), MONGODB®, Redis, Apache Cassandra®, HBASE® byAPACHE®, MapR-DB by the MAPR® corporation, or any other suitabledatabase product. Moreover, any database may be organized in anysuitable manner, for example, as data tables or lookup tables. Eachrecord may be a single file, a series of files, a linked series of datafields, or any other data structure.

Association of certain data may be accomplished through any desired dataassociation technique such as those known or practiced in the art. Forexample, the association may be accomplished either manually orautomatically. Automatic association techniques may include, forexample, a database search, a database merge, GREP, AGREP, SQL, using akey field in the tables to speed searches, sequential searches throughall the tables and files, sorting records in the file according to aknown order to simplify lookup, and/or the like. The association stepmay be accomplished by a database merge function, for example, using a“key field” in pre-selected databases or data sectors. Various databasetuning steps are contemplated to optimize database performance. Forexample, frequently used files such as indexes may be placed on separatefile systems to reduce In/Out (“I/O”) bottlenecks.

More particularly, a “key field” partitions the database according tothe high-level class of objects defined by the key field. For example,certain types of data may be designated as a key field in a plurality ofrelated data tables and the data tables may then be linked on the basisof the type of data in the key field. The data corresponding to the keyfield in each of the linked data tables is preferably the same or of thesame type. However, data tables having similar, though not identical,data in the key fields may also be linked by using AGREP, for example.In accordance with one embodiment, any suitable data storage techniquemay be utilized to store data without a standard format. Data sets maybe stored using any suitable technique, including, for example, storingindividual files using an ISO/IEC 7816-4 file structure; implementing adomain whereby a dedicated file is selected that exposes one or moreelementary files containing one or more data sets; using data setsstored in individual files using a hierarchical filing system; data setsstored as records in a single file (including compression, SQLaccessible, hashed via one or more keys, numeric, alphabetical by firsttuple, etc.); data stored as Binary Large Object (BLOB); data stored asungrouped data elements encoded using ISO/IEC 7816-6 data elements; datastored as ungrouped data elements encoded using ISO/IEC Abstract SyntaxNotation (ASN.1) as in ISO/IEC 8824 and 8825; other proprietarytechniques that may include fractal compression methods, imagecompression methods, etc.

In various embodiments, the ability to store a wide variety ofinformation in different formats is facilitated by storing theinformation as a BLOB. Thus, any binary information can be stored in astorage space associated with a data set. As discussed above, the binaryinformation may be stored in association with the system or external tobut affiliated with system. The BLOB method may store data sets asungrouped data elements formatted as a block of binary via a fixedmemory offset using either fixed storage allocation, circular queuetechniques, or best practices with respect to memory management (e.g.,paged memory, least recently used, etc.). By using BLOB methods, theability to store various data sets that have different formatsfacilitates the storage of data, in the database or associated with thesystem, by multiple and unrelated owners of the data sets. For example,a first data set which may be stored may be provided by a first party, asecond data set which may be stored may be provided by an unrelatedsecond party, and yet a third data set which may be stored, may beprovided by an third party unrelated to the first and second party. Eachof these three exemplary data sets may contain different informationthat is stored using different data storage formats and/or techniques.Further, each data set may contain subsets of data that also may bedistinct from other subsets.

As stated above, in various embodiments, the data can be stored withoutregard to a common format. However, the data set (e.g., BLOB) may beannotated in a standard manner when provided for manipulating the datain the database or system. The annotation may comprise a short header,trailer, or other appropriate indicator related to each data set that isconfigured to convey information useful in managing the various datasets. For example, the annotation may be called a “condition header,”“header,” “trailer,” or “status,” herein, and may comprise an indicationof the status of the data set or may include an identifier correlated toa specific issuer or owner of the data. In one example, the first threebytes of each data set BLOB may be configured or configurable toindicate the status of that particular data set; e.g., LOADED,INITIALIZED, READY, BLOCKED, REMOVABLE, or DELETED. Subsequent bytes ofdata may be used to indicate for example, the identity of the issuer,user, transaction/membership account identifier or the like. Each ofthese condition annotations are further discussed herein.

The annotation may also be used for other types of status information aswell as various other purposes. For example, the data set annotation mayinclude security information establishing access levels. The accesslevels may, for example, be configured to permit only certainindividuals, levels of employees, companies, or other entities to accessdata sets, or to permit access to specific data sets based on thetransaction, merchant, issuer, user, or the like. Furthermore, thesecurity information may restrict/permit only certain actions such asaccessing, modifying, and/or deleting data sets. In one example, thedata set annotation indicates that only the data set owner or the userare permitted to delete a data set, various identified users may bepermitted to access the data set for reading, and others are altogetherexcluded from accessing the data set. However, other access restrictionparameters may also be used allowing various entities to access a dataset with various permission levels as appropriate.

The data, including the header or trailer, may be received by astandalone interaction device configured to add, delete, modify, oraugment the data in accordance with the header or trailer. As such, inone embodiment, the header or trailer is not stored on the transactiondevice along with the associated issuer-owned data but instead theappropriate action may be taken by providing to the user at thestandalone device, the appropriate option for the action to be taken.The system may contemplate a data storage arrangement wherein the headeror trailer, or header or trailer history, of the data is stored on thesystem, device or transaction instrument in relation to the appropriatedata.

One skilled in the art will also appreciate that, for security reasons,any databases, systems, devices, servers, or other components of thesystem may consist of any combination thereof at a single location or atmultiple locations, wherein each database, system, device, server,and/or other component includes any of various suitable securityfeatures, such as firewalls, access codes, encryption, decryption,compression, decompression, and/or the like.

Encryption may be performed by way of any of the techniques nowavailable in the art or which may become available—e.g., Twofish, RSA,El Gamal, Schorr signature, DSA, PGP, PM, GPG (GnuPG), HPEFormat-Preserving Encryption (FPE), Voltage, Triple DES, Blowfish, AES,MD5, HMAC, IDEA, RC6, and symmetric and asymmetric cryptosystems. Thesystems and methods may also incorporate SHA series cryptographicmethods, elliptic-curve cryptography (e.g., ECC, ECDH, ECDSA, etc.),and/or other post-quantum cryptography algorithms under development.

A firewall may include any hardware and/or software suitably configuredto protect CMS components and/or enterprise computing resources fromusers of other networks. Further, the firewall may be configured tolimit or restrict access to various systems and components behind thefirewall for web clients connecting through a web server. The firewallmay reside in varying configurations including Stateful Inspection,Proxy based, access control lists, and Packet Filtering among others.The firewall may be integrated within a web server or any other CMScomponents or may further reside as a separate entity. The firewall mayimplement network address translation (“NAT”) and/or network addressport translation (“NAPT”). The firewall may accommodate varioustunneling protocols to facilitate secure communications, such as thoseused in virtual private networking. The firewall may implement ademilitarized zone (“DMZ”) to facilitate communications with a publicnetwork such as the internet. The firewall may be integrated as softwarewithin an internet server, any other application server components ormay reside within another computing device or may take the form of astandalone hardware component.

The system and method may be described herein in terms of functionalblock components, screen shots, optional selections, and variousprocessing steps. It should be appreciated that such functional blocksmay be realized by any number of hardware and/or software componentsconfigured to perform the specified functions. For example, the systemmay employ various integrated circuit components, e.g., memory elements,processing elements, logic elements, look-up tables, and the like, whichmay carry out a variety of functions under the control of one or moremicroprocessors or other control devices. Similarly, the softwareelements of the system may be implemented with any programming orscripting language such as C, C++, C#, JAVA®, JAVASCRIPT®, JAVASCRIPT®Object Notation (JSON), VBScript, Macromedia COLD FUSION, COBOL,MICROSOFT® company's Active Server Pages, assembly, PERL®, PHP, awk,PYTHON®, Visual Basic, SQL Stored Procedures, PL/SQL, any UNIX® shellscript, and extensible markup language (XML) with the various algorithmsbeing implemented with any combination of data structures, objects,processes, routines or other programming elements. Further, it should benoted that the system may employ any number of conventional techniquesfor data transmission, signaling, data processing, network control, andthe like. Still further, the system could be used to detect or preventsecurity issues with a client-side scripting language, such asJAVASCRIPT®, VBScript, or the like. Cryptography and network securitymethods are well known in the art, and are covered in many standardtexts.

In various embodiments, the software elements of the system may also beimplemented using NODE.JS® components. NODE.JS® programs may implementseveral modules to handle various core functionalities. For example, apackage management module, such as NPM®, may be implemented as an opensource library to aid in organizing the installation and management ofthird-party NODE.JS® programs. NODE.JS® programs may also implement aprocess manager, such as, for example, Parallel Multithreaded Machine(“PM2”); a resource and performance monitoring tool, such as, forexample, Node Application Metrics (“appmetrics”); a library module forbuilding user interfaces such as for example REACHJS®; and/or any othersuitable and/or desired module.

As will be appreciated by one of ordinary skill in the art, the systemmay be embodied as a customization of an existing system, an add-onproduct, a processing apparatus executing upgraded software, astand-alone system, a distributed system, a method, a data processingsystem, a device for data processing, and/or a computer program product.Accordingly, any portion of the system or a module may take the form ofa processing apparatus executing code, an internet based embodiment, anentirely hardware embodiment, or an embodiment combining aspects of theinternet, software, and hardware. Furthermore, the system may take theform of a computer program product on a computer-readable storage mediumhaving computer-readable program code means embodied in the storagemedium. Any suitable computer-readable storage medium may be utilized,including hard disks, CD-ROM, SONY BLU-RAY DISC®, optical storagedevices, magnetic storage devices, and/or the like.

The term “non-transitory” is to be understood to remove only propagatingtransitory signals per se from the claim scope and does not relinquishrights to all standard computer-readable media that are not onlypropagating transitory signals per se. Stated another way, the meaningof the term “non-transitory computer-readable medium” and“non-transitory computer-readable storage medium” should be construed toexclude only those types of transitory computer-readable media whichwere found in In re Nuijten to fall outside the scope of patentablesubject matter under 35 U.S.C. § 101.

Benefits, other advantages, and solutions to problems have beendescribed herein with regard to specific embodiments. However, thebenefits, advantages, solutions to problems, and any elements that maycause any benefit, advantage, or solution to occur or become morepronounced are not to be construed as critical, required, or essentialfeatures or elements of the disclosure. The scope of the disclosure isaccordingly limited by nothing other than the appended claims, in whichreference to an element in the singular is not intended to mean “one andonly one” unless explicitly so stated, but rather “one or more.”Moreover, where a phrase similar to ‘at least one of A, B, and C’ or ‘atleast one of A, B, or C’ is used in the claims or specification, it isintended that the phrase be interpreted to mean that A alone may bepresent in an embodiment, B alone may be present in an embodiment, Calone may be present in an embodiment, or that any combination of theelements A, B and C may be present in a single embodiment; for example,A and B, A and C, B and C, or A and B and C.

Although the disclosure includes a method, it is contemplated that itmay be embodied as computer program instructions on a tangiblecomputer-readable carrier, such as a magnetic or optical memory or amagnetic or optical disk. All structural, mechanical, electrical, andfunctional equivalents to the elements of the above-described variousembodiments that are known to those of ordinary skill in the art areexpressly incorporated herein by reference and are intended to beencompassed by the present claims. Moreover, it is not necessary for adevice or method to address each and every problem sought to be solvedby the present disclosure, for it to be encompassed by the presentclaims. Furthermore, no element, component, or method step in thepresent disclosure is intended to be dedicated to the public regardlessof whether the element, component, or method step is explicitly recitedin the claims. No claim element is intended to invoke 35 U.S.C. § 112(f)unless the element is expressly recited using the phrase “means for” or“step for”. As used herein, the terms “comprises,” “comprising,” or anyother variation thereof, are intended to cover a non-exclusiveinclusion, such that a process, method, article, or apparatus thatcomprises a list of elements does not include only those elements butmay include other elements not expressly listed or inherent to suchprocess, method, article, or apparatus.

What is claimed is:
 1. A method, comprising: receiving, by a blockchainAPI host, a request to create a partnership smart contract, wherein therequest comprises a partnership parameter; propagating, by theblockchain API host, a contract request to consensus participants forwriting to a blockchain, wherein the contract request comprises thepartnership smart contract, and wherein the partnership smart contractcomprises the partnership parameter; and transmitting, by the blockchainAPI host, a contract write notification to a loyalty portal, wherein inresponse to receiving the contract write notification the loyalty portalbroadcasts a partnership notification to a qualifying participant basedon the partnership parameter.
 2. The method of claim 1, furthercomprising: receiving, by the blockchain API host, a request for anactive partnership smart contract, wherein the request comprises loyaltypartner data; retrieving, by the blockchain API host, the activepartnership smart contract by comparing the partnership parameter of theactive partnership smart contract with the loyalty partner data; andreturning, by the blockchain API host, the active partnership smartcontract to a loyalty partner.
 3. The method of claim 1, furthercomprising: receiving, by the blockchain API host, a partnershipenrollment request, wherein the partnership enrollment request comprisesloyalty partner data and a partnership smart contract identifier; andpropagating, by the blockchain API host, the partnership enrollmentrequest to the consensus participants for writing to the blockchain,wherein in response to receiving the partnership enrollment request theconsensus participants achieve consensus on the partnership enrollmentrequest.
 4. The method of claim 1, further comprising: executing, by theblockchain API host, the partnership smart contract in response to beinginvoked by a first loyalty partner, wherein the first loyalty partnerinvokes the blockchain API host in response to completing a firsttransaction with a customer, and wherein in response to being executedthe partnership smart contract records the first transaction; andpropagating, by the blockchain API host, a first transaction recordwrite to the consensus participants for writing to the blockchain,wherein in response to receiving the first transaction record write theconsensus participants achieve consensus on the first transaction recordwrite.
 5. The method of claim 4, further comprising: executing, by theblockchain API host, the partnership smart contract in response to beinginvoked by a second loyalty partner, wherein the second loyalty partnerinvokes the blockchain API host in response to completing a secondtransaction with the customer, and wherein in response to being executedthe partnership smart contract records the second transaction; andpropagating, by the blockchain API host, a second transaction recordwrite to the consensus participants for writing to the blockchain,wherein in response to receiving the second transaction record write theconsensus participants achieve consensus on the second transactionrecord write.
 6. The method of claim 5, wherein in response to beingexecuted the partnership smart contract determines that the firsttransaction and the second transaction complete the partnershipparameter of the partnership smart contract.
 7. The method of claim 6,wherein in response to a purchase reward of the partnership smartcontract being a loyalty point payout the partnership smart contractinstructs blockchain API host to adjust a loyalty account balance of thecustomer based on the loyalty point payout.
 8. The method of claim 1,wherein the partnership parameter comprises at least one of a qualifyingparticipant parameter, a purchase requirement parameter, a purchasereward parameter, or a partnership duration parameter.
 9. A loyaltypoint network, comprising: a processor; and a tangible, non-transitorymemory configured to communicate with the processor, the tangible,non-transitory memory having instructions stored thereon that, inresponse to execution by the processor, cause a blockchain API host toperform operations comprising: receiving, by the blockchain API host, arequest to create a partnership smart contract, wherein the requestcomprises a partnership parameter; propagating, by the blockchain APIhost, a contract request to consensus participants for writing to ablockchain, wherein the contract request comprises the partnership smartcontract, and wherein the partnership smart contract comprises thepartnership parameter; and transmitting, by the blockchain API host, acontract write notification to a loyalty portal, wherein in response toreceiving the contract write notification the loyalty portal broadcastsa partnership notification to a qualifying participant based on thepartnership parameter.
 10. The loyalty point network of claim 9, furthercomprising: receiving, by the blockchain API host, a request for anactive partnership smart contract, wherein the request comprises loyaltypartner data; retrieving, by the blockchain API host, the activepartnership smart contract by comparing the partnership parameter of theactive partnership smart contract with the loyalty partner data; andreturning, by the blockchain API host, the active partnership smartcontract to a loyalty partner.
 11. The loyalty point network of claim 9,further comprising: receiving, by the blockchain API host, a partnershipenrollment request, wherein the partnership enrollment request comprisesloyalty partner data and a partnership smart contract identifier; andpropagating, by the blockchain API host, the partnership enrollmentrequest to the consensus participants for writing to the blockchain,wherein in response to receiving the partnership enrollment request theconsensus participants are configured to achieve consensus on thepartnership enrollment request.
 12. The loyalty point network of claim9, further comprising: executing, by the blockchain API host, thepartnership smart contract in response to being invoked by a firstloyalty partner, wherein the first loyalty partner is configured toinvoke the blockchain API host in response to completing a firsttransaction with a customer, and wherein in response to being executedthe partnership smart contract is configured to record the firsttransaction; and propagating, by the blockchain API host, a firsttransaction record write to the consensus participants for writing tothe blockchain, wherein in response to receiving the first transactionrecord write the consensus participant are configured to achieveconsensus on the first transaction record write.
 13. The loyalty pointnetwork of claim 12, further comprising: executing, by the blockchainAPI host, the partnership smart contract in response to being invoked bya second loyalty partner, wherein the second loyalty partner isconfigured to invoke the blockchain API host in response to completing asecond transaction with the customer, and wherein in response to beingexecuted the partnership smart contract is configured to record thesecond transaction; and propagating, by the blockchain API host, asecond transaction record write to the consensus participants forwriting to the blockchain, wherein in response to receiving the secondtransaction record write the consensus participants are configured toachieve consensus on the second transaction record write.
 14. Theloyalty point network of claim 13, wherein in response to being executedthe partnership smart contract is configured to determine whether thefirst transaction and the second transaction complete the partnershipparameter of the partnership smart contract.
 15. The loyalty pointnetwork of claim 14, wherein in response to a purchase reward of thepartnership smart contract being a loyalty point payout the partnershipsmart contract is configured to instruct blockchain API host to adjust aloyalty account balance of the customer based on the loyalty pointpayout.
 16. An article of manufacture including a non-transitory,tangible computer readable storage medium having instructions storedthereon that, in response to execution by a blockchain API host, causethe blockchain API host to perform operations comprising: receiving, bythe blockchain API host, a request to create a partnership smartcontract, wherein the request comprises a partnership parameter;propagating, by the blockchain API host, a contract request to consensusparticipants for writing to a blockchain, wherein the contract requestcomprises the partnership smart contract, and wherein the partnershipsmart contract comprises the partnership parameter; and transmitting, bythe blockchain API host, a contract write notification to a loyaltyportal, wherein in response to receiving the contract write notificationthe loyalty portal broadcasts a partnership notification to a qualifyingparticipant based on the partnership parameter.
 17. The article of claim16, further comprising: executing, by the blockchain API host, thepartnership smart contract in response to being invoked by a firstloyalty partner, wherein the first loyalty partner is configured toinvoke the blockchain API host in response to completing a firsttransaction with a customer, and wherein in response to being executedthe partnership smart contract is configured to record the firsttransaction; and propagating, by the blockchain API host, a firsttransaction record write to the consensus participants for writing tothe blockchain, wherein in response to receiving the first transactionrecord write the consensus participant are configured to achieveconsensus on the first transaction record write.
 18. The article ofclaim 17, further comprising: executing, by the blockchain API host, thepartnership smart contract in response to being invoked by a secondloyalty partner, wherein the second loyalty partner is configured toinvoke the blockchain API host in response to completing a secondtransaction with the customer, and wherein in response to being executedthe partnership smart contract is configured to record the secondtransaction; and propagating, by the blockchain API host, a secondtransaction record write to the consensus participants for writing tothe blockchain, wherein in response to receiving the second transactionrecord write the consensus participants are configured to achieveconsensus on the second transaction record write.
 19. The article ofclaim 18, wherein in response to being executed the partnership smartcontract is configured to determine whether the first transaction andthe second transaction complete the partnership parameter of thepartnership smart contract.
 20. The article of claim 19, wherein inresponse to a purchase reward of the partnership smart contract being aloyalty point payout the partnership smart contract is configured toinstruct blockchain API host to adjust a loyalty account balance of thecustomer based on the loyalty point payout.